dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-13457

HIGH · 7.5 CVSS v3.1 Published 2026-01-10
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
The WooCommerce Square plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.1 via the get_token_by_id function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to expose arbitrary Square "ccof" (credit card on file) values and leverage this value to potentially make fraudulent charges on the target site.

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 WooCommerce Square plugin for WordPress is vulnerable to Insecure Direct Object Reference (IDOR) in the get_token_by_id function in all versions up to 5.1.1. The function lacks validation on a user-controlled key parameter, allowing unauthenticated attackers to retrieve arbitrary Square 'ccof' (credit card on file) tokens. These exposed tokens could be leveraged to make fraudulent charges on affected sites.

MitigationUpdate the WooCommerce Square plugin to version 5.1.2 or later to address the missing validation. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious requests to the vulnerable endpoint.

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. Confirm WooCommerce Square plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate the WooCommerce Square plugin. Note its current version displayed there.
    Affected if Plugin is installed and active, regardless of version
  2. Check installed plugin version
    Compare the installed version number to the affected range. The vulnerability affects all versions up to 5.1.1. The fixed version is 5.1.2.
    Affected if Installed version is 5.1.1 or lower
  3. Verify Square payment gateway is enabled
    Navigate to WooCommerce > Settings > Payments in WordPress admin. Check if the Square payment gateway is enabled and configured.
    Affected if Square payment gateway is active and configured to accept payments
  4. Check for unauthenticated token retrieval exposure
    The vulnerability allows unauthenticated requests to retrieve Square 'ccof' tokens via the get_token_by_id function. Inspect any available logs or access records for unusual requests to Square-related API endpoints.
    Affected if Unusual or unauthorized API calls to token retrieval endpoints are observed in logs

You are affected if the WooCommerce Square plugin version is 5.1.1 or lower and the Square payment gateway is enabled, as the vulnerable get_token_by_id function lacks validation on the key parameter.

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 WooCommerce Square plugin to version 5.1.2 or later to address the missing validation. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious requests to the vulnerable endpoint.

Recommended fix Moderate confidence

WooCommerce Square version 5.1.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WooCommerce Square plugin
  4. Check the current version installed (should be 5.1.1 or below)
  5. Update the plugin to the latest available version (5.1.2 or higher) which contains the security patch
  6. Verify the update was successful by confirming the new version number
Caveat Standard minor version update - review plugin changelog for any related functionality changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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