Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
S:C chosen because unauthenticated injection executes in admin browser session, crossing a privilege boundary; A:N since XSS causes no direct availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
The Autopay WordPress plugin before 5.0.1 does not perform any capability or nonce check before saving a styling option from a public request, and does not escape that value when it is later output on the checkout page, allowing unauthenticated attackers to store JavaScript that executes in the browser of any user, including administrators, who loads the checkout page.
AnalysisAI
Stored cross-site scripting in the Autopay WordPress plugin before 5.0.1 permits unauthenticated attackers to permanently inject arbitrary JavaScript into a site's checkout page by exploiting a missing capability check and nonce validation on a styling option endpoint. The injected payload executes in the browser of every visitor - including administrators - who loads the checkout page, enabling session hijacking, credential theft, or unauthorized admin actions. …
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 | Exploitation requires a WordPress installation with the Autopay plugin installed, active, and running a version below 5.0.1; the checkout page must be publicly accessible, which is standard for any live WooCommerce or payment plugin deployment. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a network-reachable, unauthenticated, low-complexity attack requiring only that a victim visit the checkout page. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An unauthenticated attacker identifies a WordPress site running the Autopay plugin and sends a crafted HTTP POST request to the plugin's public-facing styling option endpoint, embedding a malicious JavaScript payload (e.g., a cookie-stealing script) in the styling value. The payload is stored server-side with no validation. … |
| Remediation | Update the Autopay WordPress plugin to version 5.0.1 or later immediately; this vendor-released patch addresses both the missing authorization/nonce check and the absent output escaping, per WPScan's advisory at https://wpscan.com/vulnerability/99fa208c-1a6f-4379-847c-388b9cec349e/ and VulDB entry at https://vuldb.com/vuln/387300. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all WordPress installations using Autopay and identify sites running versions prior to 5.0.1; consider temporarily disabling the plugin if versions cannot be immediately confirmed. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Stored XSS in the Autopay (Platnosci Online Blue Media) WordPress plugin through version 5.0.0 permits unauthenticated r
Unauthenticated XSS in the Autopay WordPress plugin (versions ≤ 5.0.0) enables remote attackers to inject and execute ar
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-54994
GHSA-pmwm-pj73-5hr6