← All security briefings

Attention

Accept Stripe Payments through 2.1.4 allows stored XSS through comment links, fixed in 2.1.5

Identifiers: CVE-2026-130323

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Accept Stripe Payments, the WordPress plugin with slug stripe-payments from Tips and Tricks HQ, is affected through version 2.1.4 inclusive under CVE-2026-130323. Wordfence Intelligence disclosed the issue on November 20, 2026. Links in comments submitted by unauthenticated users can cause script to run in a viewer's browser only when an affected page renders such a link and, in the usual path, the viewer clicks it. The fix is in 2.1.5. The developer changelog on wordpress.org confirms related changes to popup and prefetch link construction without naming the CVE. This concerns the WordPress plugin only and does not indicate any incident on Stripe's platform or any payment-card breach.

Classification reason: A fix is available in 2.1.5. Wordfence Intelligence disclosed the issue on November 20, 2026 and the developer changelog confirms related changes. No reviewed source reports exploitation.

Impact

Script executes in the browser of a user who views a page where an attacker-supplied comment link is rendered. In the disclosed path this usually requires the user to click the affected link. When the non-default Prefetch Payment Popup Scripts option is enabled and such a link is present on the page, the vulnerable code may run while the page loads, without a click. The effect stays within the viewer's browser and is not server-side code execution. No reviewed source shows observed exploitation.

Who is affected

Applies to sites running Accept Stripe Payments 2.1.4 or earlier where a comment link from an untrusted commenter is rendered on a page. With default settings, the disclosed path requires a viewer to click that link. The separate page-load path applies only when the non-default Prefetch Payment Popup Scripts option is enabled and such a link is present on the page. Enabling prefetch alone, without affected comment content, does not establish exposure.

Products and versions

Products and versionsAffectedFixed
Accept Stripe Payments <=2.1.4 2.1.5

Exploitation evidence

Exploitation not established. No reviewed source reports observed exploitation. The disclosed path depends on untrusted comment links being rendered and typically on a user clicking one. The non-default prefetch setting, when enabled, removes the click requirement.

Sources: Wordfence Intelligence

Actions

  1. Verify the installed plugin is Accept Stripe Payments (slug stripe-payments) and note the exact version from the Plugins screen.
  2. Back up the site, update to 2.1.5 or a newer patched release, then run the normal checkout flow in the maintainer's usual test environment and confirm the payment popup opens and completes as expected.
  3. Review comment moderation to see whether links from untrusted commenters are currently visible, and keep new comments pending moderation until the update is in place.
  4. Check whether the Prefetch Payment Popup Scripts option is enabled. Turning it off reduces the no-click path while the patch is arranged, but the click path remains, so this is not a substitute for updating.

Unknowns

  • The exact plugin version and whether the prefetch option is enabled on any given site.
  • What publicly visible comment content, including links, currently exists on each site.
  • No reviewed source reports exploitation, but absence of reports is not proof that none occurred.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/stripe-payments/accept-stripe-payments-214-unauthenticated-stored-dom-based-cross-site-scripting-via-comment-link-href-attribute
  • Team Tips and Tricks HQ on WordPress.org · retrieved https://wordpress.org/plugins/stripe-payments/#developers
  • CVE Program, assigned by Wordfence · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-130323

Change history

  1. — Published: November 22, 2026: Brief created from the Wordfence Intelligence disclosure and the developer changelog on wordpress.org. Affected through 2.1.4, fixed in 2.1.5. No evidence of exploitation found in the reviewed sources.

Subscribe: RSS feed · JSON Feed · Feed format and fields