CVE-2021-47983: WordPress Plugin Stripe Payments 2.0.39 Stored XSS via currency_code
WordPress Plugin Stripe Payments 2.0.39 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts through the AcceptStripePayments-settings[currency_code] parameter. Attackers can submit POST requests to /wp-admin/options.php with script payloads in the currency_code field to execute arbitrary JavaScript in administrator browsers when settings are viewed.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47983 affects the WordPress Accept Stripe Payments plugin version 2.0.39. An authenticated user can store JavaScript in a currency setting, causing it to run in an administrator’s browser when settings are viewed. This can support account abuse or site configuration tampering, but requires WordPress access.
Executive priority
Treat as a near-term WordPress remediation item, especially for revenue-generating sites using Stripe payments. It is not rated critical, but stored XSS in admin workflows can enable meaningful compromise if an attacker already has site access.
Technical view
The issue is stored cross-site scripting in AcceptStripePayments-settings[currency_code] submitted to WordPress options handling. Sources identify CWE-79, CVSS 3.1 score 6.4, and scope change with low confidentiality and integrity impact. A public ExploitDB entry exists, but the bundle does not show CISA KEV listing or confirmed active exploitation.
Likely exposure
Exposure is limited to WordPress sites running Accept Stripe Payments version 2.0.39 where lower-privileged authenticated users can submit or influence plugin settings/options. Internet exposure of WordPress increases targeting likelihood, but authentication is required.
Exploitation context
A public exploit reference is available, so defenders should assume the technique is documented. However, the provided sources do not confirm active exploitation in the wild, and the CVE is not marked as KEV.
Researcher notes
Evidence supports stored XSS in version 2.0.39 via currency_code. Public exploit material exists, but do not equate that with observed exploitation. Patch status is not established in the supplied sources; validate against the WordPress plugin developer changelog before asserting fixed versions.
Mitigation direction
Inventory WordPress sites for Accept Stripe Payments version 2.0.39.
Check the plugin developer page and vendor guidance for fixed versions or official remediation.
Upgrade or replace the plugin only following vendor-supported guidance.
Restrict access to WordPress admin and plugin settings to trusted administrators.
Review and remove suspicious script-like content from affected plugin settings.
Validation and detection
Confirm whether Accept Stripe Payments 2.0.39 is installed.
Verify who can edit WordPress options or plugin settings.
Inspect the currency_code setting for unexpected HTML or JavaScript content.
After remediation, confirm settings pages render without executing stored script content.
Monitor admin account activity for unexpected changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.