Skip to main content

Quick PayPal Payments CVE-2026-110017

| EUVDEUVD-2026-102659 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-16 Wordfence GHSA-q8wf-34g4-mm3w
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor-level account
  2. Delivery
    Inject quote-breaking payload via 'form' parameter
  3. Exploit
    Payload bypasses wp_kses_post and is stored
  4. Execution
    Admin/Editor previews pending post
  5. Persist
    Script executes in privileged session
  6. Impact
    Session hijack or privilege escalation

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress account with Contributor-level privileges or higher on a site running Quick PayPal Payments ≤6.0.4, and the attacker must submit a payload through the plugin's 'form' parameter. The payload must be quote-breaking and contain no angle brackets to survive the wp_kses_post filter. Successful impact against privileged users additionally depends on an Editor or Administrator viewing/previewing the attacker's injected post - a routine moderation action for pending Contributor content, but still a dependency. The primary limiting factor is the Contributor authentication requirement: sites that do not allow untrusted users to register as Contributors are not practically exposed.

Impact

This is a moderate-severity stored XSS (CVSS 6.4) that reflects a genuine but constrained risk rather than a critical priority. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C) indicates network-reachable, low-complexity exploitation, but PR:L is the decisive limiter: an attacker must already hold an authenticated Contributor-or-above account, which means this is not an unauthenticated internet-wide threat. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization - no public exploit identified at time of analysis. The notable amplifying factor, well-supported by the description, is the privilege-escalation pathway: because wp_kses_post strips only angle-bracket tags, a quote-breaking payload survives post save, and the script executes when higher-privileged Editors or Administrators preview a Contributor's pending content, enabling potential account/session takeover despite the modest C:L/I:L rating. Net assessment: patch in normal cycle for sites that permit untrusted Contributor registrations; lower urgency for sites where all content authors are trusted.

Exploit ScenarioDerived

An attacker registers or obtains a Contributor account on a target WordPress site and creates a draft post embedding a quote-breaking JavaScript payload via the plugin's vulnerable 'form' parameter, which bypasses wp_kses_post because it contains no angle brackets. When an Editor or Administrator previews the pending post for moderation, the stored script executes in their authenticated browser session. No public exploit code was identified, though the low attack complexity (AC:L) makes manual exploitation straightforward.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Stored cross-site scripting in the Quick PayPal Payments: Payment Button & Form WordPress plugin (all versions up to and including 6.0.4) allows authenticated attackers holding Contributor-level access or higher to inject arbitrary JavaScript through the plugin's 'form' parameter, which then executes for every viewer of the affected post. The sanitization bypass is notable because the payload survives wp_kses_post by using a quote-breaking, angle-bracket-free construction, so injected script fires even for Editors and Administrators who routinely preview a Contributor's pending content. No public exploit code has been identified at time of analysis, and this is a moderate-severity (CVSS 6.4) issue whose practical exposure depends on whether a site permits untrusted users to register or be assigned the Contributor role.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - the correction was committed to plugin trunk via WordPress.org changeset 3746507 (https://plugins.trac.wordpress.org/changeset/3746507 and https://plugins.trac.wordpress.org/changeset/3746507/quick-paypal-payments/trunk/legacy/quick-paypal-payments.php, touching legacy/quick-paypal-payments.php), so administrators should update the plugin to the first published release above 6.0.4 as soon as it is available in the WordPress.org repository; do not rely on 6.0.4, which is explicitly in scope. If an update cannot be applied immediately, the most effective compensating control is to eliminate the required privilege: restrict or disable new Contributor registrations and audit existing accounts, since the attack vector demands an authenticated Contributor-or-higher session (side effect: legitimate guest authors lose publishing capability). On sites that do not use the plugin, deactivate and delete it, which removes the attack surface entirely with no functional loss. Additionally, restrict the ability to preview pending content to trusted roles where operationally feasible, and review existing posts authored by Contributors for stored angle-bracket-free, quote-breaking payloads in the plugin's 'form' field, removing any suspicious content - noting that content sanitization alone is not a substitute for the upstream patch because wp_kses_post does not filter this payload class. Vendor and reporter guidance is available at https://www.wordfence.com/threat-intel/vulnerabilities/id/203f850e-1eed-4c49-b733-4ac2ce9b6772?source=cve, and standard WordPress hardening such as disabling unfiltered HTML for lower roles and deploying a content security policy can reduce but not eliminate the execution of injected script (side effect: CSP may break legitimate inline plugin scripts and requires careful testing).

Affected VersionsENISA

Quick PayPal Payments: Payment Button & Form 0 ≤6.0.4

Affected Packages

euvd quick_paypal_payments_payment_button_form no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the WordPress plugin 'quick-paypal-payments' from vendor fullworks (CPE cpe:2.3:a:fullworks:quick_paypal_payments:_payment_button_&_form), specifically the legacy code path in legacy/quick-paypal-payments.php at the routines around lines 603, 826, 1546 and 1554, where the 'form' parameter is accepted and later emitted into page output. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), a classic stored/persistent XSS: user-supplied input is stored in post content and re-rendered without adequate contextual output escaping. WordPress core's wp_kses_post filter is applied but only strips HTML tags - it does not neutralize a quote-breaking payload that contains no angle brackets, so the crafted value passes through the save path intact and is later concatenated into an attribute or script context where the injected quote terminates the legitimate context and the attacker's JavaScript executes. Because the payload persists in the database, exploitation is persistent rather than reflected, and the CVSS vector (S:C, PR:L, UI:N) reflects a scope change on impact for the browser security context with only low confidentiality and integrity impact and no availability impact. Exploitation requires an authenticated session with Contributor-level privileges or above and submission through the plugin's 'form' parameter; delivery to high-privilege victims additionally depends on an Editor or Administrator viewing or previewing the injected post, which is a routine moderation workflow for pending Contributor submissions.

Know when Quick Paypal Payments gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Contributor authentication gives PR:L; filter bypass needs no special conditions so AC:L; stored script crossing into a victim's browser session justifies S:C with C:L/I:L and no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Quick PayPal Payments: Payment Button & Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form' parameter in all versions up to, and including, 6.0.4 due to insufficient input sanitization and output escaping. 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. Because wp_kses_post strips only HTML tags, a quote-breaking payload containing no angle brackets survives post save intact, and the injected script fires for every viewer of the post - including higher-privileged Editors and Administrators who routinely preview a Contributor's pending content.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche single-vendor WordPress PayPal payment plugin, limited install base
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy