CVE-2025-13739
CryptX <= 4.0.5 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The CryptX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `cryptx` shortcode in all versions up to, and including, 4.0.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- d3395 CryptX
through 4.0.5
References 6
plugins.trac.wordpress.org
- browser/cryptx/tags/4.0.4/classes/CryptX.php#L149
- browser/cryptx/tags/4.0.4/classes/CryptX.php#L237
- browser/cryptx/tags/4.0.4/classes/CryptX.php#L604
- browser/cryptx/tags/4.0.4/classes/CryptX.php#L1295
- changeset?sfp_email=&sfph_mail=&reponame=&old=3416363%40cryptx&new=3416363%40cryptx&sfp_email=&sfph_mail=