dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62870

MEDIUM · 5.3 CVSS v3.1 Published 2025-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 →
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
Missing Authorization vulnerability in Eupago Eupago Gateway For Woocommerce eupago-gateway-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Eupago Gateway For Woocommerce: from n/a through <= 4.7.1.

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

Missing authorization vulnerability in the Eupago Gateway For WooCommerce plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to and including 4.7.1, enabling unauthorized access to functionality that should be restricted by proper access controls.

MitigationImplement proper authorization checks on all sensitive endpoints and functionality within the plugin, and update to a patched version once released by the vendor.

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. Verify Eupago Gateway For WooCommerce is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Eupago Gateway For WooCommerce' in the list of active plugins.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/eupago-gateway-for-woocommerce/ folder for the version number.
    Affected if The version is 4.7.1 or lower (any version up to and including 4.7.1)
  3. Identify exposed administrative endpoints
    Review the plugin files for any AJAX handlers, REST API routes, or admin pages that handle sensitive operations. Check for functions that process payments, refunds, or configuration changes without verifying user capabilities.
    Affected if The plugin exposes administrative functionality that can be accessed without proper capability checks
  4. Test for unauthorized access to restricted functions
    Attempt to access plugin functions using a low-privilege user account (e.g., subscriber or customer role) to see if sensitive operations can be triggered without admin-level permissions.
    Affected if Non-administrator users can access functionality intended only for administrators

You are affected if the Eupago Gateway For WooCommerce plugin version 4.7.1 or lower is installed and the plugin exposes sensitive endpoints or functions without proper capability 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 authorization checks on all sensitive endpoints and functionality within the plugin, and update to a patched version once released by the vendor.

Recommended fix Moderate confidence

Update to the latest available version of Eupago Gateway For WooCommerce (version higher than 4.7.1)

  1. 1. Log in to the WordPress admin dashboard where the Eupago Gateway For WooCommerce plugin is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Eupago Gateway For WooCommerce' in the plugin list
  4. 4. Check the current installed version (displayed under the plugin name)
  5. 5. If the installed version is 4.7.1 or below, click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository or Eupago's official source
  6. 6. After updating, verify the new version number confirms the update was successful
  7. 7. Test the payment gateway functionality to ensure the update did not break any existing WooCommerce payment processing
Caveat Unknown - test payment functionality after updating to ensure compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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