Skip to content
Noroxi

Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions

wp-full-stripe-free · plugin

Known security vulnerabilities for Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions. Find out in seconds which version runs on your site with WP Lens.

9 known vulnerabilities

5 exploitable without logging in · 2 with public exploit code · latest Oct 1, 2026

Listed on wordpress.org · latest 8.5.7 · last updated Sep 30, 2026 · 8K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

  • CVE-2023-47667unauthenticated · needs a click≤ 7.0.16

    WordPress WP Full Stripe Free plugin <= 7.0.16 - Cross Site Request Forgery (CSRF) vulnerability on every Setting Save

    High 8.8

  • CVE-2025-58789high privilege≤ 8.2.5

    WordPress WP Full Stripe Free Plugin <= 8.2.5 - SQL Injection Vulnerability

    High 7.6

  • CVE-2026-62073unauthenticated≤ 8.5.6

    WordPress WP Full Stripe Free plugin <= 8.5.6 - Broken Access Control vulnerability

    High 7.5

  • CVE-2025-9322unauthenticated≤ 8.3.1

    Stripe Payment Forms <= 8.3.1 - Unauthenticated SQL Injection

    High 7.5

  • CVE-2026-61960unauthenticated · needs a click≤ 8.5.0

    WordPress WP Full Stripe Free plugin <= 8.5.0 - Cross Site Scripting (XSS) vulnerability

    High 7.1

  • CVE-2026-42378login required≤ 8.4.1

    WordPress WP Full Stripe Free plugin <= 8.4.1 - Broken Authentication vulnerability

    Medium 6.5

  • CVE-2026-12432unauthenticated≤ 8.4.3

    Stripe Payment Forms by WP Full Pay <= 8.4.3 - Missing Authorization to Unauthenticated Payment Record Manipulation via 'paymentIntentId' Parameter

    Medium 5.3

  • CVE-2023-46088admin≤ 1.6.1

    WordPress WP Full Stripe Free Plugin <= 1.6.1 is vulnerable to Cross Site Scripting (XSS)

    Medium 4.8

  • CVE-2023-28934admin≤ 1.6.1

    WordPress WP Full Stripe Free Plugin <= 1.6.1 is vulnerable to Cross Site Scripting (XSS)

    Medium 4.8

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory