Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or compromise Contributor account
-
DeliveryInject XSS payload via plugin input field
-
ExploitPayload stored in WordPress database
-
ExecutionAdmin views or approves affected content
-
PersistScript executes in admin browser
-
ImpactSession cookie exfiltrated or admin actions performed
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 the attacker to hold a WordPress Contributor-level account (or higher) on the target site - confirmed by the CVSS PR:L metric. The Virtue/Ascend/Pinnacle Toolkit plugin must be installed and active (version 4.9.12 or earlier). A privileged user (editor, administrator) must subsequently interact with the attacker-controlled content - confirmed by CVSS UI:R. Exploitation is limited to WordPress installations running this specific plugin; sites that do not use the Virtue, Ascend, or Pinnacle themes or their associated toolkit plugin are not affected. Open contributor registration (WordPress setting 'Anyone can register' combined with default Contributor role assignment) significantly expands the attacker pool; closed-registration sites require social engineering or credential compromise to obtain the necessary access. |
| Impact | The NVD-assigned CVSS 3.1 score of 6.5 (Medium) reflects a realistic threat profile: network-accessible (AV:N), low complexity (AC:L), but gated behind contributor-level WordPress authentication (PR:L) and requiring victim interaction (UI:R). The scope change (S:C) with C:L/I:L/A:L understates the practical session-hijacking risk - a successful XSS against an administrator can yield full site takeover beyond what C:L implies. No EPSS data was provided in the intelligence feed, and the vulnerability does not appear in the CISA KEV catalog, indicating no confirmed widespread active exploitation. No POC code was referenced. The realistic risk is moderate-to-elevated for multi-author WordPress sites (blogs, publications, agencies) where contributor accounts are granted to untrusted or semi-trusted users; for single-author or tightly controlled installations the attack surface is minimal. The A:L component in the provided CVSS vector is contestable - standard XSS exploitation does not typically produce availability impact; this may be inflated. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a WordPress Contributor account on a target site crafts a post or widget input containing a malicious JavaScript payload and saves it via the Virtue/Ascend/Pinnacle Toolkit plugin's input fields. When a site administrator reviews, approves, or simply views the affected content in their authenticated browser session, the injected script executes, enabling the attacker to steal the administrator's session cookie, perform actions on their behalf, or redirect the admin to a credential-harvesting page. No public POC has been identified, but the low complexity (AC:L) and standard XSS class make independent exploitation straightforward for anyone with basic web security knowledge. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Cross-site scripting in the Nexcess Virtue/Ascend/Pinnacle Toolkit WordPress plugin (versions up to and including 4.9.12) allows authenticated contributors to inject malicious scripts that execute in the browser sessions of higher-privileged users such as administrators. The CVSS vector (PR:L/UI:R/S:C) confirms the attack requires WordPress Contributor-level access and victim interaction, but achieves a scope change - meaning the payload runs in the victim's browser context outside the plugin's own trust boundary. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis, though the Patchstack disclosure provides an actionable reference for affected site operators.
RemediationAI
Operators should upgrade the Virtue/Ascend/Pinnacle Toolkit plugin beyond version 4.9.12 as the primary remediation; however, no specific fixed release version was identified in the available intelligence data - consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/virtue-toolkit/vulnerability/wordpress-virtue-ascend-pinnacle-toolkit-plugin-4-9-12-cross-site-scripting-xss-vulnerability?_s_id=cve and the WordPress.org plugin repository for the latest available release. As a compensating control pending patch availability, restrict the Contributor role to fully trusted users only, or temporarily demote existing contributor accounts to Subscriber - this eliminates the PR:L entry point. Enabling a Web Application Firewall (WAF) rule targeting XSS payloads (e.g., via Wordfence or Patchstack's virtual patching feature) can block exploit attempts without requiring a plugin update, though WAF bypasses are possible and this is not a substitute for patching. Review existing contributor-submitted content for anomalous script tags or event handler attributes.
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 the Virtue/Ascend/Pinnacle Toolkit WordPress plugin, identified by CPE cpe:2.3:a:nexcess:virtue/ascend/pinnacle_toolkit:*:*:*:*:*:*:*:* and maintained under the Nexcess vendor umbrella to support the Virtue, Ascend, and Pinnacle commercial WordPress themes. CWE-79 (Improper Neutralization of Input During Web Page Generation) is the root cause class, meaning contributor-supplied input is reflected or stored and later rendered without adequate output encoding or sanitization in the HTML response. The scope change (S:C) in the CVSS vector is characteristic of stored or DOM-based XSS where injected payload executes in a victim's browser context that is governed by a different origin or privilege boundary than the plugin itself - commonly observed when an editor or contributor can embed script payloads that an administrator later views on the front-end or in the admin dashboard.
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:L
AV:N and AC:L reflect straightforward network-based WordPress exploitation; PR:L confirmed by Contributor role requirement; UI:R from admin interaction needed; S:C for browser scope change; A:N because XSS does not cause availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Cross Site Scripting (XSS) in Virtue/Ascend/Pinnacle Toolkit <= 4.9.12 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.
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-48085
GHSA-h83f-3329-47h2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB