CVE-2025-13739
BaseFortify
Publication date: 2025-12-05
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpres | cryptx | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the CryptX plugin for WordPress. It occurs because the plugin does not properly sanitize or escape user-supplied input in its 'cryptx' shortcode. As a result, authenticated users with contributor-level access or higher can inject malicious scripts into pages, which then execute whenever any user views those pages.
How can this vulnerability impact me? :
The vulnerability allows attackers with contributor-level access to inject malicious scripts into WordPress pages. This can lead to unauthorized actions such as stealing user credentials, hijacking user sessions, defacing websites, or spreading malware to visitors, thereby compromising the security and integrity of the affected website.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying the presence of the CryptX WordPress plugin version 4.0.4 or earlier and checking for usage of the `cryptx` shortcode with potentially malicious attributes. Since the vulnerability is a Stored Cross-Site Scripting via shortcode attributes, you can scan WordPress content for the `[cryptx]` shortcode and inspect attributes for suspicious scripts. Commands to detect the plugin version and shortcode usage might include: 1) Using WP-CLI to list installed plugins and their versions: `wp plugin list | grep cryptx` 2) Searching the WordPress database for posts containing the shortcode: `wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[cryptx%';"` 3) Using grep on the WordPress files to confirm plugin version: `grep 'Version:' wp-content/plugins/cryptx/cryptx.php` 4) Monitoring HTTP requests for unusual script execution or injected payloads in pages using the shortcode. These steps help detect vulnerable plugin versions and potential exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Updating the CryptX plugin to a version later than 4.0.4 where the vulnerability is fixed. 2) If an update is not immediately available, disable or remove the CryptX plugin to prevent exploitation. 3) Review and sanitize any content using the `[cryptx]` shortcode to remove malicious scripts. 4) Limit contributor-level access or higher to trusted users only, as the vulnerability requires authenticated contributor-level access. 5) Monitor logs and site content for signs of injected scripts and remove any detected malicious content. These steps reduce the risk of exploitation until a patch is applied. [2]