Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious 'fvrt_' parameter URL
-
DeliveryDeliver link via phishing to logged-in user
-
ExploitVictim clicks, parameter reflected unescaped
-
ExecutionScript executes in victim browser session
-
ImpactHijack session or perform admin actions
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 | Exploitation requires an attacker to deliver a crafted URL containing a malicious payload in any 'fvrt_'-prefixed request parameter of a site running Favicon Rotator ≤1.2.11, and to trick a user into clicking that link (UI:R) - the script only executes in the clicking victim's browser. No authentication is required of the attacker (PR:N) and no special plugin configuration is needed beyond having the vulnerable plugin installed and active, but the dependence on social-engineering a victim click and the reflected (non-persistent) nature are the key factors limiting real-world impact. Impact scales with the victim's privileges: an administrator victim yields the most damage. |
| Impact | This is a textbook moderate-severity reflected XSS (CVSS 6.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) that should be treated as a routine, lower-priority patch rather than an emergency. The network vector and lack of required privileges (PR:N) make it reachable by unauthenticated attackers, but the mandatory user interaction (UI:R) - the victim must click a crafted link - substantially lowers real-world risk, which is why confidentiality and integrity impact are only Low and availability is None. No EPSS score, SSVC decision, or KEV listing was provided in the input, and no public exploit was supplied, so there is no public exploit identified at time of analysis; the absence of exploitation telemetry is consistent with a non-targeted, low-urgency flaw. The signals are internally consistent (no CVSS-versus-description conflict), so the main caveat is simply that exploitation probability data (EPSS) is missing and cannot be used to further refine prioritization. |
| Exploit ScenarioDerived | An attacker crafts a URL to a vulnerable site that embeds a malicious script in an 'fvrt_'-prefixed request parameter and distributes it via phishing, social media, or a malicious page. When a logged-in administrator or other user clicks the link, the unsanitized parameter is reflected into the page and the script executes in their browser session, potentially stealing cookies or performing actions on their behalf. No public exploit code was provided, and exploitation depends on successfully luring a victim to click (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Reflected cross-site scripting in the Favicon Rotator plugin for WordPress (all versions up to and including 1.2.11) allows unauthenticated attackers to inject arbitrary JavaScript through any request parameter prefixed with 'fvrt_', which the plugin reflects back into a page without adequate sanitization or output escaping. Exploitation is not direct: because the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, the attacker must deliver a crafted link and convince a victim to click it, after which the script executes only in that victim's browser, potentially stealing session data, altering page content, or acting as the victim - with an administrator victim yielding the greatest impact. This is a moderate-severity reflected XSS that warrants routine, lower-priority patching; no public exploit code was identified at time of analysis, and the vendor's 1.2.12 release addresses the flaw.
RemediationAI
Vendor-released patch: 1.2.12 - upgrade the Favicon Rotator plugin to version 1.2.12 or later, which is the version referenced in the official WordPress.org changeset that diffs against the vulnerable 1.2.11 tag. In a standard WordPress deployment this means applying the available plugin update from the Plugins screen or via WP-CLI; because the plugin remains functional across the update, there is little operational reason to delay, though this should still be scheduled as a routine maintenance action rather than an emergency response given the moderate severity. If the update cannot be applied immediately, the most effective compensating control is to deactivate and, if unused, delete the plugin - this fully removes the attack surface but sacrifices the favicon rotation feature; a less disruptive alternative is to place a WAF or reverse-proxy rule that blocks or strips request parameters beginning with 'fvrt_' on inbound traffic, with the trade-off that any legitimate plugin functionality relying on those parameters may break and the rule must be maintained to avoid false positives. Site administrators should also follow the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/96fd3647-e006-430e-8252-6bd79263e02a?source=cve and the changeset at https://plugins.trac.wordpress.org/changeset?reponame=&new=3515020%40favicon-rotator%2Ftags%2F1.2.12&old=3118754%40favicon-rotator%2Ftags%2F1.2.11 for confirmation of the fix. Note that because the issue is reflected rather than stored, there is no database cleanup or cache purge required after patching.
Affected VersionsENISA
Affected Packages
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 flaw is a classic CWE-79 improper neutralization of input during web page generation (reflected cross-site scripting) in a PHP-based WordPress plugin. Favicon Rotator uses a namespaced family of request parameters prefixed with 'fvrt_' (its own short prefix), and at least one of these parameters is echoed back into the generated HTML page without being passed through WordPress escaping functions such as esc_attr(), esc_html(), or equivalent sanitization. Because the vulnerable data path is reflective rather than stored, nothing is persisted to the database - the payload travels in the crafted URL and lives only for the duration of the request, which is why the CVSS vector scores UI:R (the victim must click) and S:C (the injected script runs in the context of the rendered page and can affect resources beyond the vulnerable component). The CPE cpe:2.3:a:archetyped:favicon_rotator:*:*:*:*:*:*:*:* identifies the affected product as the 'favicon_rotator' plugin published by vendor 'archetyped', with the wildcard version indicating that every release through 1.2.11 is in scope. No authentication is required of the attacker (PR:N) and no exotic plugin configuration is needed beyond the plugin being installed and active; the exploitability constraints are the social-engineering step and the non-persistent nature of the injection.
Know when Favicon Rotator 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
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Unauthenticated network-delivered reflected XSS (AV:N/PR:N) requiring a victim click (UI:R), executing in the browser context for a scope change (S:C) with Low C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Favicon Rotator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'fvrt_' prefixed request parameters in all versions up to, and including, 1.2.11 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-96214
GHSA-m5rr-w32q-pc8f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB