dbcve.org
Quick Paypal PaymentsWordPress extension · Fullworksplugins

CVE-2023-23889

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-25
Fix available
A fix is available. Upgrade to 5.7.26 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Paypal Payments plugin <= 5.7.25 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated users with contributor-level access can inject malicious JavaScript code through the plugin's input fields. The payload gets stored in the database and executes when other users (including administrators) view affected pages in the WordPress admin or frontend.

MitigationUpdate the Fullworks Quick PayPal Payments plugin to a version newer than 5.7.25, which should include proper input sanitization and output encoding to prevent XSS.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Quick Paypal PaymentsWordPress extension
Affected:< 5.7.26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    Check wp-content/plugins/quick-paypal-payments/ directory exists, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The Quick PayPal Payments plugin by Fullworks is present
  2. Determine installed version
    Read the main plugin file header in wp-content/plugins/quick-paypal-payments/quick-paypal-payments.php and look for 'Version:' tag, or check the plugin details page in WordPress admin
    Affected if Version number is below 5.7.26
  3. Check for stored XSS in plugin database entries
    Query WordPress posts/meta tables for script tags or javascript: URIs in fields associated with the plugin (look in wp_postmeta with meta_key containing 'quick_paypal' or related plugin-specific keys)
    Affected if Malicious script tags or event handlers are found stored in plugin-related database entries
  4. Inspect plugin-generated frontend/admin pages
    View pages where Quick PayPal Payments shortcodes or widgets are rendered; view page source and look for unsanitized user input being output in HTML attributes or content
    Affected if User-supplied data appears unescaped in HTML output (visible script tags, event handlers like onerror/onload, or foreign characters indicating lack of encoding)
  5. Review user role permissions for plugin settings
    Navigate to the plugin settings page and verify if contributor-level users have access to create or modify payment forms/campaigns
    Affected if Contributor role users can access and modify plugin input fields without administrator oversight

The environment is affected if the Quick PayPal Payments plugin version is below 5.7.26 and contributor-level users have access to plugin input fields that accept and store unsanitized content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.7.26 or later
Fixed in 5.7.26
Interim mitigation

Update the Fullworks Quick PayPal Payments plugin to a version newer than 5.7.25, which should include proper input sanitization and output encoding to prevent XSS.

Recommended fix High confidence

Quick Paypal Payments version 5.7.26

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate the 'Quick Paypal Payments' plugin in the plugins list
  4. Check if version 5.7.26 is available as an update (the vulnerability is fixed in this version)
  5. Click 'Update Now' to upgrade the plugin to version 5.7.26
  6. Verify the plugin updated successfully to version 5.7.26
  7. Test the PayPal payment functionality to ensure the plugin still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Quick Paypal Payments Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23889 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data