Skip to main content

Magic Tooltips CF7 EUVDEUVD-2026-91906

| CVE-2026-101928 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-03 Wordfence GHSA-9r93-q577-w4r2
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit comment with entity-encoded script
  2. Delivery
    Set payload as author name
  3. Exploit
    Bypasses sanitize_text_field, stored in DB
  4. Execution
    Admin opens wp-admin/edit-comments.php
  5. Persist
    esc_html decodes payload to live HTML
  6. Impact
    Script runs in admin session

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a WordPress site running Magic Tooltips For Contact Form 7 version 1.0.34 or earlier with comment submission enabled (WordPress default). The attacker submits a comment containing an HTML-entity-encoded script in the 'author' name field; no authentication is needed for submission. The payload only executes when a privileged administrator opens the comment-moderation screen at wp-admin/edit-comments.php, where the plugin's esc_html callback decodes the entities into executable markup - this admin-view requirement is the key limiting factor. Comment moderation does NOT mitigate it, because pending/unapproved comments still render in the moderation queue the admin reviews.

Impact

CVSS 3.1 rates this 7.2 (High), driven by AV:N/AC:L/PR:N (unauthenticated, network, low complexity) plus S:C for scope change - an unauthenticated visitor's input executes in the authenticated administrator's browser context. However, several signals temper real-world urgency: no EPSS score was provided, the CVE is not in CISA KEV (no confirmed active exploitation), and no public exploit code was supplied, so exploitation status is 'no public exploit identified at time of analysis.' Applying an SSVC lens: exploitation is 'none' (no evidence in the wild), the attack is not readily automatable because a privileged administrator must view the comment-moderation queue before the payload fires, and technical impact is partial (C:L/I:L, no availability loss). A notable data nuance: the input vector lists UI:N, yet the description makes clear execution only occurs when an administrator views wp-admin/edit-comments.php - a privileged user action that argues for UI:R and a somewhat lower effective score. Net assessment: a legitimate stored-XSS admin-takeover risk worth patching promptly, but tempered to medium real-world priority by low product prevalence, the admin-view trigger, and the absence of exploitation or EPSS evidence.

Exploit ScenarioDerived

An unauthenticated attacker submits a WordPress comment whose author-name field contains an HTML-entity-encoded script payload (e.g. using '<tip>'-style encoding); this passes sanitize_text_field because it is inert text at submission time. When a site administrator later opens the comment-moderation screen (wp-admin/edit-comments.php), the plugin's esc_html filter callback decodes the entities back into live HTML and the script executes in the administrator's authenticated session, enabling actions such as creating rogue admin accounts. No public proof-of-concept was provided in the intelligence sources; the low attack complexity (AC:L) and network vector (AV:N) make exploitation straightforward once an admin views the queue.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 03, 2026

Stored cross-site scripting (XSS) in the Magic Tooltips For Contact Form 7 plugin for WordPress (versions up to and including 1.0.34) allows unauthenticated attackers to inject arbitrary JavaScript that executes in an administrator's browser when they view the comment moderation screen at wp-admin/edit-comments.php. The flaw exists because the plugin's esc_html filter callback decodes HTML-entity-encoded payloads (e.g., '<tip>') back into live HTML, so an entity-encoded script submitted as a comment author name bypasses sanitize_text_field and is rendered as executable markup. Exploitation requires the site to have comment submission enabled (WordPress default) and a privileged administrator to open the moderation queue; no public exploit code or active exploitation is identified at time of analysis, though the CVSS score of 7.2 (High) reflects the unauthenticated, network-based attack vector and scope change.

RemediationAI

Update the Magic Tooltips For Contact Form 7 plugin to a version later than 1.0.34. An upstream fix is available via WordPress plugin repository changeset 3723483 at https://plugins.trac.wordpress.org/changeset?reponame=&old=3723483%40magic-tooltips-for-contact-form-7&new=3723483%40magic-tooltips-for-contact-form-7, which resolves the entity-decoding behavior; however, the exact patched version number is not independently confirmed in the provided data. If immediate updating is not possible, consider disabling comment submissions entirely (though this breaks a core WordPress feature) or restrict comment author names to alphanumeric characters using a custom filter, which will block the attack but may reject legitimate names with special characters. Additionally, a Web Application Firewall rule can be configured to block comment submissions containing HTML-entity-encoded script tags in the author field, but this may generate false positives for comments that legitimately include such entities. Note that comment moderation does not mitigate the issue, as pending comments are rendered in the moderation queue that the administrator views.

Affected VersionsENISA

Magic Tooltips For Contact Form 7 0 ≤1.0.34

Affected Packages

euvd magic_tooltips_for_contact_form_7 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) in a WordPress plugin context. The Magic Tooltips For Contact Form 7 plugin extends Contact Form 7 by adding tooltips, and it overrides the WordPress esc_html filter through a callback defined in lib/wp-hooks.php (line 96). That callback is intended to safely encode HTML output, but it also decodes HTML entities back into their corresponding characters, effectively undoing the encoding. This means that when an attacker submits a comment with an author name containing entity-encoded HTML like '<script>', the WordPress sanitize_text_field function (which does not decode entities) allows the payload through. Later, when the plugin's filter processes the comment author field for display, it decodes the entities, turning the payload into live script tags. The CPE string cpe:2.3:a:magicplugins:magic_tooltips_for_contact_form_7:*:*:*:*:*:*:*: identifies the plugin as the affected component, and all versions up to and including 1.0.34 are vulnerable. The CVSS vector shows AV:N (network), AC:L (low complexity), PR:N (unauthenticated), S:C (scope change), and C:L/I:L/A:N, indicating that the attacker's input executes in the administrator's browser context, crossing a privilege boundary.

Know when Magic Tooltips For Contact Form 7 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Unauthenticated remote comment injection gives AV:N/AC:L/PR:N; execution requires an admin to view the moderation page, so UI:R; payload runs in admin context across a trust boundary, hence S:C with C:L/I:L.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Magic Tooltips For Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author' parameter in all versions up to, and including, 1.0.34 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because the plugin's esc_html filter callback decodes HTML-entity-encoded payloads (e.g. those containing '<tip>') back into live HTML, meaning an entity-encoded script payload submitted as a comment author name - which bypasses sanitize_text_field - is rendered as executable markup when an administrator views wp-admin/edit-comments.php.

Executive ViewAI

Why It Matters

A stored cross-site scripting flaw in the Magic Tooltips For Contact Form 7 WordPress plugin (versions up to and including 1.0.34) lets anyone on the internet plant malicious JavaScript that runs inside a logged-in administrator's browser the moment they open the comment moderation screen. Because no vendor patch is available and the attack needs only the site's default comment submission feature, any WordPress site running this plugin is exposed, and a successful compromise of an administrator session can lead to full site takeover, defacement, or data theft. Leadership should treat this as an active exposure requiring interim mitigations while the vendor remediates.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Magic Tooltips For Contact Form 7 plugin (versions up to and including 1.0.34); disable comment submissions or require full moderation if the plugin must stay active; restrict access to wp-admin/edit-comments.php by IP allowlist or VPN; enforce multi-factor authentication for administrator accounts; and deploy WAF rules blocking entity-encoded script payloads in comment author fields.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Low
niche Contact Form 7 add-on plugin, small install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy