dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-25714

HIGH · 7.5 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Fullworks Quick Paypal Payments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Quick Paypal Payments: from n/a through 5.7.25.

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

This is a Missing Authorization (Broken Access Control) vulnerability in the Quick PayPal Payments WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain functionality, likely allowing unauthenticated or lower-privileged users to access administrative or sensitive payment functions that should be restricted to higher-privileged users.

MitigationImplement proper capability checks and role-based access controls (RBAC) on all sensitive plugin functions and AJAX endpoints to ensure only authorized WordPress user roles can access payment-related functionality.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Quick PayPal Payments plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm 'Quick PayPal Payments' is installed and active, or inspect the filesystem at wp-content/plugins/ for the plugin directory
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the plugin version
    In WordPress admin > Plugins, click on the plugin to view its version details, or open the main plugin PHP file and look for a version constant or header comment
    Affected if The installed version falls within any affected version range (compare against known vulnerable versions if available)
  3. Test AJAX endpoints for missing authorization
    Use a tool like curl or Burp Suite to send requests to common WordPress AJAX endpoints (admin-ajax.php) with the plugin's action parameters, while authenticated as a low-privilege user (subscriber or editor) or unauthenticated
    Affected if The AJAX actions return successful responses or perform actions that should require administrator privileges
  4. Inspect plugin source code for capability checks
    Review the main plugin PHP files and look for function calls like current_user_can(), check_admin_referer(), or other WordPress capability/authorization functions before executing sensitive operations
    Affected if Sensitive functions (payment processing, settings changes, user data access) lack proper current_user_can() or equivalent authorization checks

The site is affected if the Quick PayPal Payments plugin is installed and its sensitive endpoints or functions can be accessed or executed by unauthenticated users or lower-privileged WordPress users without proper authorization verification.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and role-based access controls (RBAC) on all sensitive plugin functions and AJAX endpoints to ensure only authorized WordPress user roles can access payment-related functionality.

Recommended fix Moderate confidence

Version 5.7.26 or later

  1. 1. Check the current version of the Quick Paypal Payments plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Quick Paypal Payments plugin and note the current version number
  4. 4. If the installed version is 5.7.25 or earlier, update to version 5.7.26 or later
  5. 5. Update via WordPress admin: Go to Plugins > Add New > Upload, or use the built-in updater
  6. 6. Alternatively, update via FTP/SFTP by uploading the new plugin files to wp-content/plugins/quick-paypal-payments/
  7. 7. After updating, verify the new version number in the plugins list
  8. 8. Test the plugin functionality to ensure the authorization controls are working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25714 — 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-25714 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