dbcve.org
Quick Paypal PaymentsWordPress extension · Fullworksplugins

CVE-2023-25713

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-07
Fix available
A fix is available. Upgrade to 5.7.26 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. 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 · moderate confidence

An unauthenticated stored Cross-Site Scripting (XSS) vulnerability exists in the Fullworks Quick PayPal Payments WordPress plugin versions 5.7.25 and earlier. Attackers can inject malicious JavaScript code into plugin input fields that gets stored in the database and executed when administrators or other users view affected pages, potentially leading to session hijacking or administrative account compromise.

MitigationUpdate the Fullworks Quick PayPal Payments plugin to the latest version (greater than 5.7.25) to remediate this vulnerability. Until patched, monitor admin pages for suspicious user-generated content and consider disabling the plugin if updates are not available.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm plugin installation
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Quick PayPal Payments' by Fullworks. Alternatively, check if the directory /wp-content/plugins/quick-paypal-payments/ exists on the server, or run: wp plugin list --search='quick-paypal-payments'
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, find the plugin on the Plugins page and read the version number displayed beneath the plugin name. Or read the main plugin file header in /wp-content/plugins/quick-paypal-payments/quick-paypal-payments.php, or run: wp plugin get quick-paypal-payments --field=version
    Affected if Version is 5.7.25 or lower (anything below 5.7.26)
  3. Determine if plugin input forms are publicly accessible
    Visit the WordPress site frontend and look for any payment forms, donation buttons, or input fields added by the Quick PayPal Payments plugin. Check pages where the plugin shortcode (typically [quick_paypal_payments] or similar) is used. The vulnerability is unauthenticated, meaning anyone can submit to these forms.
    Affected if Public-facing input forms from the plugin are present and accessible to anonymous users
  4. Audit stored data for suspicious content
    If forms exist, examine the WordPress database (wp_posts table) or plugin-specific database tables for any entries containing <script> tags, javascript:, or other XSS vectors in fields that would be rendered back to users. Use a database query or admin tools like phpMyAdmin to search for patterns like '%<script%' in content that may have been submitted through the plugin forms.
    Affected if Malicious script tags or XSS payloads are found stored in the database originating from plugin input fields

The environment is affected if the Quick PayPal Payments plugin version 5.7.25 or earlier is installed and its input forms are exposed on the site, allowing stored XSS payloads to be injected and executed.

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 the latest version (greater than 5.7.25) to remediate this vulnerability. Until patched, monitor admin pages for suspicious user-generated content and consider disabling the plugin if updates are not available.

Recommended fix High confidence

5.7.26

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Quick Paypal Payments' plugin
  4. Click 'Update Now' if an update is available, or manually update to version 5.7.26
  5. Verify the plugin is running version 5.7.26 after updating

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-25713 — 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-25713 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