DTX – Dynamic Text Extension for Contact Form 7
contact-form-7-dynamic-text-extension · plugin
Known security vulnerabilities for DTX – Dynamic Text Extension for Contact Form 7. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
4 exploitable without logging in · 1 with no official fix seen · latest Oct 10, 2026
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 4 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 5.0.7 · last updated Aug 4, 2026 · 100K+ installs
wordpress.org status checked on Nov 20, 2026
Vulnerabilities
- High 7.5
CVE-2026-62043unauthenticated≤ 5.0.7
WordPress Contact Form 7 – Dynamic Text Extension plugin <= 5.0.7 - Sensitive Data Exposure vulnerability
- Medium 6.5
CVE-2025-13146unauthenticatedno fix seen
Contact Form 7 – Dynamic Text Extension <= 5.0.7 - Unauthenticated Arbitrary Shortcode Execution
- Medium 5.3
CVE-2025-63068unauthenticated≤ 5.0.5
WordPress Contact Form 7 Dynamic Text Extension plugin <= 5.0.5 - Content Injection vulnerability
- Medium 4.4
CVE-2026-5116editor+≤ 5.0.5
Contact Form 7 – Dynamic Text Extension <= 5.0.5 - Authenticated (Editor+) Stored Cross-Site Scripting
- Medium 4.3
CVE-2024-56218unauthenticated · needs a click≤ 5.0.1
WordPress Contact Form 7 - Dynamic Text Extension plugin <= 5.0.1 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2024-10084contributor+≤ 4.5
Contact Form 7 – Dynamic Text Extension <= 4.5 - Information Disclosure via Shortcode
- Medium 4.3
CVE-2023-6630contributor+≤ 4.1.0
Contact Form 7 – Dynamic Text Extension <= 4.1.0 - Insecure Direct Object Reference
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (5.0.7) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.