WordPress Sala theme <= 1.1.3 - PHP Object Injection Vulnerability

published 2025-06-27 last yr. modified 2026-06-17 4mo ago also EUVD-2025-19314

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits: 0; none known

Deserialization of Untrusted Data vulnerability in uxper Sala allows Object Injection. This issue affects Sala: from n/a through 1.1.3.

Is CVE-2025-52826 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2025-06-27)

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

uxper Sala

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/theme/sala/vulnerability/wordpress-sala-1-1-3-php-object-injection-vulnerability?_s_id=cve
vdb-entry

Sources

CVE List CVE-2025-52826
NVD CVE-2025-52826

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.