Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13739: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in d3395 CryptX

0
Medium
VulnerabilityCVE-2025-13739cvecve-2025-13739cwe-79
Published: Fri Dec 05 2025 (12/05/2025, 09:27:02 UTC)
Source: CVE Database V5
Vendor/Project: d3395
Product: CryptX

Description

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.4 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.

AI-Powered Analysis

AILast updated: 12/12/2025, 10:50:30 UTC

Technical Analysis

CVE-2025-13739 is a stored cross-site scripting vulnerability identified in the CryptX plugin for WordPress, affecting all versions up to and including 4.0.4. The root cause is insufficient sanitization and escaping of user-supplied input within the plugin's 'cryptx' shortcode attributes. This flaw allows authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the injected scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the context of the affected site. The vulnerability has a CVSS 3.1 base score of 6.4, reflecting medium severity, with an attack vector of network (remote), low attack complexity, requiring privileges (contributor or above), no user interaction, and a scope change due to affecting other users. The impact primarily affects confidentiality and integrity, as attackers can steal sensitive data or manipulate page content but do not disrupt availability. No public exploits have been reported yet, but the vulnerability is publicly disclosed and should be considered a credible threat. The lack of patches at the time of disclosure necessitates immediate mitigation steps to reduce risk. This vulnerability is particularly relevant for websites that allow multiple authenticated users with contributor or higher roles, as these users can exploit the flaw to compromise other users' sessions or site integrity.

Potential Impact

For European organizations, especially those operating WordPress-based websites with multiple contributors, this vulnerability poses a significant risk. Attackers with contributor access can inject malicious scripts that execute in the browsers of site visitors or administrators, potentially leading to session hijacking, theft of sensitive information, or unauthorized actions performed on behalf of legitimate users. This can result in data breaches, reputational damage, and loss of user trust. Since many European companies rely on WordPress for content management, particularly in sectors like media, education, and e-commerce, the vulnerability could affect a broad range of organizations. The medium CVSS score reflects a moderate but non-negligible risk, especially given the ease of exploitation and the scope of impact extending beyond the initial attacker. The absence of known exploits in the wild currently limits immediate widespread impact, but the public disclosure increases the likelihood of future exploitation attempts. Organizations failing to mitigate this vulnerability may face compliance issues under GDPR if personal data is compromised through such attacks.

Mitigation Recommendations

1. Immediately audit user roles and restrict contributor-level access to trusted users only, minimizing the number of users who can exploit this vulnerability. 2. Implement strict input validation and output escaping for any user-generated content, especially shortcodes, using security-focused WordPress plugins or custom code. 3. Monitor website logs and content for suspicious shortcode usage or unexpected script injections. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 5. Regularly update the CryptX plugin once a security patch is released by the vendor; in the meantime, consider disabling the plugin if feasible. 6. Educate content contributors about safe content practices and the risks of injecting untrusted code. 7. Use web application firewalls (WAFs) configured to detect and block XSS payloads targeting WordPress shortcodes. 8. Conduct periodic security assessments and penetration testing focusing on user input vectors within WordPress environments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-26T12:07:57.723Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6932a9b1f88dbe026c8e9fc9

Added to database: 12/5/2025, 9:45:21 AM

Last enriched: 12/12/2025, 10:50:30 AM

Last updated: 1/19/2026, 8:42:01 PM

Views: 109

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats