EUVD-2026-70594
GHSA-q744-qpcr-gww9
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Standard reflected/stored XSS: network-accessible, no privileges, victim interaction required, scope changed; availability impact removed as XSS does not disrupt service.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Simple Payment <= 2.5.1 versions.
AnalysisAI
Cross-site scripting in the Simple Payment WordPress plugin (versions ≤ 2.5.1) allows unauthenticated remote attackers to inject arbitrary JavaScript into pages rendered for victim users, including site administrators. The scope-changed CVSS vector (S:C) indicates the injected script executes outside the plugin's own origin - enabling session hijacking, credential theft, or administrative actions executed on the victim's behalf. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The victim must be authenticated to the WordPress site and must be induced to interact with the attacker-controlled input (e.g., visiting a crafted URL) while their session is active - this is the UI:R constraint in the CVSS vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.1 base score (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) characterizes an attack that is low-complexity and requires no attacker credentials, but does require victim interaction - typically luring an authenticated user or administrator to visit a crafted URL or page. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Administrators running Simple Payment ≤ 2.5.1 should update to the latest available version via the WordPress plugin repository, which will apply the vendor's sanitization fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all WordPress installations running Simple Payment plugin versions ≤ 2.5.1 and disable the plugin if operationally feasible; if business-critical, restrict access to trusted internal networks only. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Simple Payment
View allThe Simple Payment plugin for WordPress is vulnerable to Authentication Bypass in versions 1.3.6 to 2.3.8. This is due t
Broken access control in the Simple Payment WordPress plugin (versions 2.5.2 and below) allows unauthenticated remote at
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today