Skip to main content
Menu
CVEs

Accept Stripe Payments stored DOM-based cross-site scripting in comment link href

CVE-2026-130323Published November 21, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Accept Stripe Payments plugin for WordPress has a stored DOM-based cross-site scripting flaw that lets an unauthenticated remote attacker inject scripts through a comment link's href attribute, and those scripts run in a user's browser. Normally a user must click the attacker-placed comment link, but if the non-default "Prefetch Payment Popup Scripts" option is enabled, the script runs on page load without any user interaction.

Written by a model

Original description

The Accept Stripe Payments plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href of any <a> element containing 'asp_action=show_pp&product_id='' parameter in all versions up to, and including, 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that a user clicks the attacker-placed comment link to trigger the sink; however, if the non-default 'Prefetch Payment Popup Scripts' option is enabled, execution occurs on page load with no user interaction required.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130323 (Accept Stripe Payments <= 2.1.4 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment Link href Attribute), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130323 (entry last updated 2026-11-21):
Affected:
- mra13 Accept Stripe Payments: through 2.1.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130323 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130323 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c2f79096-3202-45a4-bf9e-e75301c1dcd3?source=cve
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/public/assets/js/stripe-handler-ng.js#L73
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/public/assets/js/stripe-handler-ng.js#L178
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/public/assets/js/stripe-handler-ng.js#L207
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/public/assets/js/stripe-handler-ng.js#L242
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/public/assets/js/stripe-handler-ng.js#L156
- https://plugins.trac.wordpress.org/browser/stripe-payments/tags/2.1.4/includes/class-asp.php#L636
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3812963%40stripe-payments&new=3812963%40stripe-payments
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130323
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130323"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 10

Questions about CVE-2026-130323

Is CVE-2026-130323 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-130323?

Accept Stripe Payments: through 2.1.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.