Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain Author-level WordPress account
-
DeliveryInject XSS payload into profile_fields_user_email_value_prefix
-
ExploitPayload persisted in author box settings
-
InstallPrivileged user visits page with author box
-
C2Victim clicks email prefix link
-
ExecuteScript executes in victim's browser context
-
ImpactSession hijack or admin privilege escalation
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 valid WordPress account with at minimum Author-level role on the target site; Contributor-level or higher also applies per the disclosure. The attacker must be able to save author box settings containing the |
| Impact | The CVSS 5.4 (Medium) score is well-calibrated for this vulnerability class. PR:L reflects the mandatory Author-level WordPress account, which limits the attack surface to sites with multiple registered contributors - a common configuration for editorial or multi-author blogs. UI:R (user must click the email link) reduces opportunistic exploitation but does not prevent targeted attacks. The critical risk amplifier is the Scope Changed (S:C) metric: an Author can plant a payload that executes in an Administrator's browser, enabling privilege escalation via XSS-driven admin takeover, nonce hijacking, or plugin installation. Without a KEV listing and no identified POC, this is a realistic but not actively weaponized threat; real-world priority is elevated for WordPress sites that grant Author or Contributor access to untrusted or externally recruited writers. EPSS data was not provided in the input and cannot be cited. |
| Exploit ScenarioDerived | An attacker registered as an Author on a multi-contributor WordPress blog edits their author box settings and injects a JavaScript payload (such as an image onerror handler or script tag) into the |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 15, 2026
Stored XSS in the PublishPress Authors WordPress plugin (all versions through 4.15.0) allows authenticated users holding Author-level access or above to inject persistent malicious scripts via the profile_fields_user_email_value_prefix parameter in author box configuration. The injected payload executes in the browser of any site user who clicks the affected author box link, enabling session hijacking, credential theft, or admin account takeover through the browser context of higher-privileged victims. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis.
RemediationAI
Upgrade the PublishPress Authors plugin to a version above 4.15.0; the exact patched release should be verified against the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/d4cc9537-879c-4c12-8b76-60241b7a3420 and the WordPress.org plugin repository, as no specific fix version is confirmed in the provided data. As a compensating control pending upgrade, administrators can restrict the Author role from modifying author box profile field prefix settings via a role-capability management plugin (e.g., User Role Editor), though this may break intended author customization workflows. Alternatively, temporarily disabling the email field display in author boxes eliminates the injection surface at the cost of removing that UI element for all authors. Sites that do not grant Author-level access to untrusted users have significantly reduced exposure.
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 vulnerability exists within the PublishPress Authors plugin's author box module, specifically in src/modules/author-boxes/author-boxes.php at approximately line 2019, as identified by the Wordfence disclosure and Trac repository reference. The profile_fields_user_email_value_prefix parameter configures a prefix string rendered alongside the author's email field in publicly-visible author boxes. CWE-79 (Improper Neutralization of Input During Web Page Generation) identifies the root cause: the prefix value is stored without adequate sanitization and later rendered without proper output escaping, allowing HTML/JavaScript injection. The CVSS S:C (Scope Changed) metric confirms the exploit crosses from the WordPress server context into the victim's browser security context. The CPE cpe:2.3:a:publishpress:co-authors,_multiple_authors_and_guest_authors_in_an_author_box_with_publishpress_authors:*:*:*:*:*:*:*:* covers all versioned releases from the initial release through 4.15.0.
Know when Wordpress Plugin 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
Author-level account required (PR:L), victim click needed (UI:R), scope changes to browser (S:C); no availability impact for stored XSS.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘profile_fields_user_email_value_prefix’ parameter in all versions up to, and including, 4.15.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user clicks 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.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-78244
GHSA-786g-g6vf-28p6
NVD
CVE.org
EPSS
Exploit-DB