CVE-2021-47983
Deferred Deferred - Pending Action
Stored XSS in Stripe Payments WordPress Plugin

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulnCheck

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-08
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
stripe payments 2.0.39
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2021-47983 is a stored cross-site scripting (XSS) vulnerability in the WordPress Plugin Stripe Payments version 2.0.39. It allows authenticated attackers to inject malicious JavaScript code through the AcceptStripePayments-settings[currency_code] parameter by submitting crafted POST requests to /wp-admin/options.php. The injected script is stored and later executed in the browsers of administrators when they view the plugin settings.

This vulnerability arises from improper neutralization of input during web page generation, classified under CWE-79.

Impact Analysis

Exploitation of this vulnerability can lead to execution of arbitrary JavaScript in administrator browsers, potentially allowing attackers to perform unauthorized actions on behalf of administrators, steal sensitive data such as cookies, or further compromise the WordPress site.

This can result in data theft, unauthorized changes to site settings, or escalation of privileges within the affected WordPress environment.

Detection Guidance

This vulnerability can be detected by checking for malicious script injections in the AcceptStripePayments-settings[currency_code] parameter via POST requests to /wp-admin/options.php.

One way to detect exploitation attempts is to monitor HTTP POST requests to /wp-admin/options.php that contain suspicious or script payloads in the currency_code field.

  • Use network monitoring tools or web server logs to filter POST requests to /wp-admin/options.php and inspect the currency_code parameter for script tags or suspicious JavaScript code.
  • Example command using grep on web server logs: grep 'POST /wp-admin/options.php' /var/log/apache2/access.log | grep 'currency_code=<script'
  • Use curl to manually test the vulnerability by sending a crafted POST request with a script payload in the currency_code parameter to see if it is stored and executed.
Mitigation Strategies

Immediate mitigation steps include restricting access to the /wp-admin/options.php page to trusted authenticated users only, as exploitation requires authentication.

Avoid using or entering untrusted input in the currency_code setting until a patch or update is applied.

Monitor and audit POST requests to /wp-admin/options.php for suspicious payloads and remove any malicious scripts found in the currency_code setting.

Update the Stripe Payments plugin to a version where this vulnerability is fixed once available.

Compliance Impact

The vulnerability is a stored cross-site scripting (XSS) flaw that allows attackers to execute arbitrary JavaScript in administrator browsers, potentially leading to unauthorized actions or data theft.

Such unauthorized access or data theft could impact compliance with data protection regulations like GDPR or HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches.

However, the provided information does not explicitly describe the direct impact of this vulnerability on compliance with these standards or any specific regulatory consequences.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2021-47983. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart