CVE-2026-8893 MEDIUM

CVE-2026-8893: Express Payment For Stripe <= 1.28.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

Vendor Payaddons
Product Express Payment For Stripe
Weakness CWE-79 · XSS
Published June 5, 2026
Last update June 6, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Express Payment For Stripe plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'type' attribute of the [stripe-express] shortcode in versions up to, and including, 1.28.0. This is due to insufficient input sanitization and output escaping on the shortcode attribute value, which is concatenated into an HTML attribute in the rendered output of the register_shortcode() function without being passed through esc_attr() or any other escaping function. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

Express Payment For Stripe versions up to 1.28.0 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other users, including administrators. The vulnerability affects the entire site scope due to how the application processes and displays user input without proper sanitization.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers and steal their session tokens or perform actions on their behalf.

Potential impact on your site

04Site Impact

Any authenticated user can compromise admin accounts and modify site content or settings through stored XSS attacks.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account on the site; no user interaction required from victims.

Key dates

06Disclosure timeline

June 5, 2026 CVE published
June 6, 2026 Record updated