Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target site
-
DeliveryInject script payload into plugin-handled field
-
ExploitStore malicious content awaiting review
-
ExecutionAdmin/editor renders content in browser
-
PersistScript executes in privileged session
-
ImpactSession hijack or account takeover
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 authenticated account with at least Contributor privileges on a WordPress site running pixfort Core before 4.3.3, plus subsequent user interaction (UI:R) from a higher-privileged user who views or moderates the attacker-supplied content, at which point the injected script executes in that victim's browser (scope change, S:C). Limiting factors: the Contributor authentication barrier means the attacker cannot be a fully anonymous outsider (sites that do not allow untrusted user registration at Contributor+ are largely insulated), and the required victim interaction makes exploitation dependent on an admin/editor rendering the malicious content rather than being automatic. |
| Impact | This is a genuine-but-low-priority issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 5.4 MEDIUM - which recomputes exactly to 5.4, so the vendor score is internally consistent) shows the two structural limiters typical of WordPress contributor-role XSS: PR:L means the attacker must already hold an authenticated Contributor (or higher) account, and UI:R means a victim - typically an admin or editor - must render the injected content. The scope change (S:C) reflects script executing in the victim's browser context against the site rather than only the plugin, but confidentiality and integrity impact are only Low and availability is None. No EPSS score, KEV listing, or POC is provided in the input, so by the precision rules this is 'no public exploit identified at time of analysis.' There is no SSVC data supplied. No signals conflict: the vector, the CWE-79 classification, and the Patchstack description all agree this is an authenticated stored/reflected XSS. This is a real-but-modest issue - patch in routine cycles - not an emergency; the authentication requirement plus required victim interaction keep real-world exploitation opportunistic and post-account-compromise rather than mass-exploitable. |
| Exploit ScenarioDerived | An attacker who has registered or acquired a Contributor-level account on a WordPress site running pixfort Core below 4.3.3 submits a post or plugin element containing a malicious script payload in an inadequately sanitized field. When an administrator or editor previews or moderates that content, the script executes in their authenticated browser session, enabling actions such as creating a rogue admin or stealing session data. No public POC or exploit code is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Stored cross-site scripting in the WordPress plugin pixfort Core affects every release before 4.3.3, letting an authenticated attacker with Contributor-level access plant script content that runs in a higher-privileged user's browser once that user views, previews, or moderates it. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, score 5.4) confirms the Contributor authentication barrier together with mandatory victim interaction, so the injected payload fires in an administrator or editor session rather than automatically - a scope-change condition that matters because the script executes with the victim's privileges. There is no indication of exploitation activity: no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS figure supplied with the source data, so this should be treated as a genuine-but-low-priority issue and handled through routine plugin update cycles.
RemediationAI
Vendor-released patch: 4.3.3 - upgrade pixfort Core to 4.3.3 or later; because the plugin is distributed through the WordPress.org update channel as a theme dependency, verify the installed version and force an update where automatic updates are disabled. If immediate patching is not possible, compensating controls are: temporarily deactivate pixfort Core where its theme-builder functionality is not required (side effect: related theme layout/template features will break), audit and reduce accounts holding Contributor or higher privileges on untrusted/self-registration sites and require manual approval before any Contributor account is created (trade-off: added editorial friction but it removes the PR:L prerequisite entirely), and apply a WAF or security-plugin rule that strips script/event-handler markup from submitted post content and plugin shortcode output (trade-off: possible false positives on legitimate embed HTML). Administrators and editors should also be cautious about previewing unreviewed contributor submissions until the update is applied, since that preview action is the UI:R trigger. Reference advisory: https://patchstack.com/database/wordpress/plugin/pixfort-core/vulnerability/wordpress-pixfort-core-plugin-4-3-3-cross-site-scripting-xss-vulnerability?_s_id=cve.
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 affected component is pixfort Core, a companion/utility plugin for pixfort's WordPress themes, distributed through the WordPress.org plugin directory and tracked by Patchstack, which reported the flaw. Root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored/persistent XSS where attacker-supplied markup is saved by the plugin and later rendered without adequate output encoding or sanitization. The distinguishing characteristic here is the WordPress capability model: the CVSS vector carries PR:L, meaning the attacker needs an account at the Contributor role or above - Contributor accounts can author and submit content but normally cannot publish it or inject unfiltered HTML, so any code path that lets a Contributor store script markup is an escaping/privilege-boundary failure rather than an anonymous-injection bug. UI:R reflects that a second, more privileged user (Editor/Administrator) must actually open or preview the stored content for the payload to execute, and S:C (scope change) captures that the script then runs in that victim's browser context with access to their session, meaning it can perform privileged actions on the victim's behalf. Sites where untrusted users cannot obtain Contributor+ accounts are substantially insulated.
Know when Pixfort Core 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:L/UI:R/S:C/C:L/I:L/A:N
Network-reachable authenticated Contributor injects script (PR:L, AC:L), victim must render it (UI:R), execution in victim's site context crosses scope (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Contributor Cross Site Scripting (XSS) in pixfort Core < 4.3.3 versions.
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-89866
GHSA-mhf5-hx6f-f9mr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB