Security readout for executives and security teams
Plain-English summary
WordPress sites using Contact Form 7 – Dynamic Text Extension up to version 5.0.6 may let unauthenticated visitors trigger unintended shortcode execution. Business impact depends on which shortcodes are installed, but the CVSS vector supports low confidentiality and integrity impact without availability impact.
Executive priority
Treat as a moderate WordPress plugin issue requiring prompt inventory and remediation. It is not currently evidenced as exploited, but unauthenticated reachability and dependency on installed shortcodes make exposure review important.
Technical view
The issue is improper validation before calling do_shortcode, allowing unauthenticated arbitrary shortcode execution. The vulnerability affects all plugin versions up to and including 5.0.6. The source bundle says version 5.0.4 only partially patched the issue.
Likely exposure
Exposure is limited to WordPress sites running Contact Form 7 – Dynamic Text Extension versions up to 5.0.6. Risk increases where installed shortcodes expose sensitive data, modify content, or perform privileged plugin behavior.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The attack is network-accessible, unauthenticated, low-complexity, and requires no user interaction, but impact depends on available shortcodes.
Researcher notes
Focus analysis on the action path that accepts user-controlled input and passes it to do_shortcode. Assess impact by enumerating registered shortcodes in the affected site context, not by assuming code execution. The partial 5.0.4 fix means version checks must include 5.0.5 and 5.0.6.
Mitigation direction
- Inventory WordPress sites for the affected plugin and version.
- Update beyond version 5.0.6 when vendor guidance confirms a complete fix.
- Disable or remove the plugin if no complete fixed release is available.
- Limit exposed form functionality where dynamic shortcode behavior is unnecessary.
- Monitor vendor, Wordfence, and WordPress plugin guidance for final remediation details.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record the installed plugin version and flag versions up to 5.0.6.
- Review shortcode-capable forms for exposure to unauthenticated visitors.
- Check web logs for unusual shortcode-like input or unexpected plugin action activity.
- Verify remediation by confirming the vulnerable version is no longer present.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-13146 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5WordfenceVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/3e5ad3a7-03c5-4085-b330-bc77e7e46cea?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/contact-form-7-dynamic-text-extension/trunk/contact-form-7-dynamic-text-extension.php#L765CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/contact-form-7-dynamic-text-extension/trunk/includes/utilities.php#L265CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3430784/CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.