CVE-2023-0557 json
ContentStudio <= 1.2.5 - Information Exposure
published 2023-01-27 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-12602
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
The ContentStudio plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.2.5. This could allow unauthenticated attackers to obtain a nonce needed for the creation of posts.
Patch / fix
- contentstudio contentstudio 1.2.6
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- plugins.trac.wordpress.org https://plugins.trac.wordpress.org/browser/contentstudio/trunk/contentstudio-plugin.php#L709 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- contentstudio ContentStudio
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset?sfp_email=&sfph_mail=&reponame=&new=2851006%40contentstudio%2Ftrunk&old=2844028%40contentstudio%2Ft
patch, third-party-advisory
-
plugins.trac.wordpress.org
/browser/contentstudio/trunk/contentstudio-plugin.php#L709
exploit, issue-tracking, third-party-advisory
- wordfence.com /threat-intel/vulnerabilities/id/62eb136f-3cb0-40dc-a154-015a7fa1077b?source=cve
-
wordfence.com
/threat-intel/vulnerabilities/id/62eb136f-3cb0-40dc-a154-015a7fa1077b
third-party-advisory
Sources
- CVE List CVE-2023-0557
- NVD CVE-2023-0557
Fencer Vulns 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.