dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15512

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-14
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 Aplazo Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the check_success_response() function in all versions up to, and including, 1.4.3. This makes it possible for unauthenticated attackers to set any WooCommerce order to `pending payment` status.

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 Aplazo Payment Gateway WordPress plugin has a missing capability check on the check_success_response() function, allowing unauthenticated attackers to invoke this function and arbitrarily set any WooCommerce order to 'pending payment' status. This is an Insecure Direct Object Reference (IDOR) combined with broken access control, as the function lacks proper authorization validation before processing order status changes.

MitigationUpdate the Aplazo Payment Gateway plugin to version 1.4.4 or later, which should include proper capability checks on the check_success_response() function. Until patched, consider restricting access to the callback endpoint via web server configuration or monitoring for unusual order status changes.

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 Aplazo Payment Gateway plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Aplazo Payment Gateway' in the list. Alternatively, check the /wp-content/plugins/ directory for an aplazo folder.
    Affected if The plugin is installed and active, making the vulnerability surface available
  2. Check the installed plugin version
    In WordPress admin_plugins list, find Aplazo Payment Gateway and note the version number displayed. Compare this to version 1.4.4.
    Affected if The installed version is lower than 1.4.4, indicating the missing capability check has not been patched
  3. Confirm WooCommerce is active
    In WordPress admin, go to Plugins and verify WooCommerce is installed and activated. The vulnerability affects WooCommerce order statuses.
    Affected if WooCommerce is active, meaning the check_success_response() function can be invoked to modify orders
  4. Review order status changes to pending payment
    In WooCommerce > Orders, filter for orders with 'Pending payment' status. Check order notes or audit logs for any status changes you did not initiate, especially in bulk or for older orders.
    Affected if Orders are found with 'Pending payment' status that were not manually set by an administrator, suggesting possible exploitation
  5. Inspect the callback endpoint accessibility
    Check your web server logs (Apache/Nginx) for requests to the Aplazo callback URL (typically /?wc-api=aplazo_check_success_response or similar). Look for unauthenticated requests from unexpected IP addresses.
    Affected if The callback endpoint is accessible to unauthenticated users and shows requests from sources you do not recognize

You are affected if the Aplazo Payment Gateway plugin is installed with a version lower than 1.4.4, WooCommerce is active, and the check_success_response() function lacks authorization checks, allowing any visitor to modify order statuses.

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 the Aplazo Payment Gateway plugin to version 1.4.4 or later, which should include proper capability checks on the check_success_response() function. Until patched, consider restricting access to the callback endpoint via web server configuration or monitoring for unusual order status changes.

Recommended fix High confidence

1.4.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Aplazo Payment Gateway plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the updated version is 1.4.4 or higher after the update completes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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