dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14078

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The PAYGENT for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.6. This is due to missing authorization checks on the paygent_check_webhook function combined with the paygent_permission_callback function unconditionally returning true on line 199. This makes it possible for unauthenticated attackers to manipulate payment callbacks and modify order statuses by sending forged payment notifications via the `/wp-json/paygent/v1/check/` endpoint.

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

The PAYGENT for WooCommerce plugin for WordPress has a missing authorization vulnerability in its REST API endpoint. The paygent_permission_callback function unconditionally returns true, allowing unauthenticated attackers to access the /wp-json/paygent/v1/check/ endpoint and manipulate payment callbacks to modify order statuses.

MitigationUpdate to version 2.4.7 or later which contains the patch. If no update is available, add proper permission_callback validation and verify payment notification authenticity before modifying order states.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check if PAYGENT for WooCommerce is installed
    Navigate to WordPress admin > Plugins, or inspect the file system at wp-content/plugins/ for a directory containing 'paygent'
    Affected if The PAYGENT for WooCommerce plugin is present on the WordPress site
  2. Verify the installed version
    In WordPress admin > Plugins, check the version listed for PAYGENT for WooCommerce. Alternatively, read the main plugin PHP file header for the 'Version' field
    Affected if The installed version is lower than 2.4.7
  3. Test unauthenticated access to the vulnerable endpoint
    Send a GET request to /wp-json/paygent/v1/check/ without providing any authentication headers or cookies, using curl or a browser
    Affected if The endpoint returns a successful response (HTTP 200) without requiring authentication
  4. Inspect the permission_callback implementation
    Locate the file containing paygent_permission_callback function (likely in the plugin's includes or api folder) and verify if it returns true unconditionally without checking user capabilities
    Affected if The function unconditionally returns true without performing any capability or authentication checks

The site is affected if PAYGENT for WooCommerce version below 2.4.7 is installed and the /wp-json/paygent/v1/check/ endpoint is accessible without authentication

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

Update to version 2.4.7 or later which contains the patch. If no update is available, add proper permission_callback validation and verify payment notification authenticity before modifying order states.

Recommended fix Moderate confidence

Version 2.4.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the PAYGENT for WooCommerce plugin
  4. Check if the current version is 2.4.6 or earlier
  5. If vulnerable, click Update Now to update to version 2.4.7 or later
  6. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from the WordPress plugin repository
  7. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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