CryptX

CryptX has one disclosed vulnerability in the WordSec catalog, all reported in 2025; it is fixed as of September 2026. Their average CVSS score is 6.4, and the most serious one scores 6.4 out of 10.

The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).

The one issue recorded for CryptX has a vendor fix available, so running the current release closes it.

All of these findings were reported by Muhammad Yudha - DJ. CryptX is installed on roughly 10,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.

Strategic Overview

Avg CVSSMedium
6.4/ 10
Patch Coverage100%
Open

0

Fixed

1

Get automatic notifications for all CryptX vulnerabilities before they are exploited.

Highest severity on recordCVSS 6.4CVE-2025-13739

CryptX <= 4.0.5 - Authenticated (Contributor+) Stored Cross-Site Scripting

Read the full analysis

Vulnerability Records

1 records
CryptX banner
Latestv4.2.1
4.4(19)
88/100
Last Updated
2026-09-11 (1d ago)
Active Installs
10,000+
Downloads
297,776
Requires WP
6.7+
Requires PHP
8.1+
Tested up to
WP 7.1
Created
2007-10-10 (19y ago)

No more SPAM by spiders scanning your site for email addresses. With CryptX you can hide all your email addresses, with and without a mailto-link, by converting them using javascript or UNICODE. CryptX protects your email addresses from spambots while keeping them readable and functional for your visitors. The plugin automatically detects email addresses in your content and encrypts them using various methods including JavaScript encryption, Unicode conversion, and image replacement. Key Features: Automatic Email Detection – Finds and encrypts email addresses in posts, pages, comments, and widgets Multiple Encryption Methods – JavaScript, Unicode, image replacement, and custom text options Widget Support – Works with text widgets and other widget content RSS Feed Control – Option to disable encryption in RSS feeds False-Positive List – Endings such as jpeg or png that keep file names like logo@2x.png from being read as addresses Exempt Addresses – Leave a single address, or a whole domain, exactly as written Per-Post Control – Enable/disable encryption on individual posts and pages Editor Block – “Protected email address”, with fields for link text, subject, cc and bcc WP-CLI – wp cryptx settings and wp cryptx scan, both per site on a network Multisite – every site keeps its own settings; a network default decides what a new one starts with Shortcode Support – Use [cryptx]email@example.com[/cryptx] for manual encryption Site Health Check – Reports whether your addresses really are hidden, measured rather than described Template Functions – Developer-friendly functions for theme integration Plugin Homepage Development The settings screen is built with React and the WordPress component library. The human-readable source ships with the plugin, so the compiled files can be rebuilt and compared: cd into the plugin directory npm install npm run build That reproduces build/index.js, build/index.css, build/index-rtl.css and build/index.asset.php byte for byte from src/. The toolchain is @wordpress/scripts; package.json and package-lock.json are included so the exact dependency versions are pinned. The front end script js/cryptx.min.js is produced from js/cryptx.js with terser@5.50.0 -c -m. js/admin-notice.js has no build step at all. It is twenty lines, it runs only in the admin, and it ships exactly as written.

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C