dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-13526

HIGH · 7.5 CVSS v3.1 Published 2025-11-22
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 OneClick Chat to Order plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0.8 via the 'wa_order_thank_you_override' function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view sensitive customer information including names, email addresses, phone numbers, billing/shipping addresses, order contents, and payment methods by simply changing the order ID in the URL.

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 OneClick Chat to Order WordPress plugin has an IDOR vulnerability in the wa_order_thank_you_override function. The plugin fails to validate or authorize order IDs supplied in the URL, allowing any unauthenticated visitor to access sensitive customer order data by simply modifying the order ID parameter.

MitigationUpdate to version 1.0.9 or later which adds proper authorization checks. Until then, consider disabling the plugin or implementing web application firewall rules to block manipulation of order-related URL parameters.

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 plugin is installed and get version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'OneClick Chat to Order', or check the plugin main file header for Version comment, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check plugin folder for version in readme.txt or main PHP file
    Affected if Plugin is installed and version is below 1.0.9
  2. Identify vulnerable endpoint exposure
    Check if the wa_order_thank_you_override function is accessible by examining plugin PHP files (typically in /wp-content/plugins/oneclick-chat-to-order/) and identifying the hooked action/filter (often a page endpoint or query var like 'wa-order-thank-you' or 'order_id' parameter)
    Affected if The plugin routes handle order ID parameters via URL without explicit authorization checks in the code
  3. Test unauthenticated order ID manipulation
    Using a browser or curl, visit the suspected thank-you page URL (commonly patterns like ?page=wa-order-thank-you&order_id=1 or similar) with different order ID values while NOT logged in, and check if order details are returned
    Affected if Order data is returned for arbitrary order IDs without requiring login or order ownership verification
  4. Verify missing authorization logic
    Review the wa_order_thank_you_override function in the plugin source code for presence of current_user_can(), wp_verify_nonce(), or order ownership validation checks before outputting order data
    Affected if No authorization or ownership validation exists before order data is displayed

User is affected if the OneClick Chat to Order plugin version is below 1.0.9 AND the order thank-you page endpoint is accessible to unauthenticated users with order data being returned for manipulated order IDs.

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 1.0.9 or later which adds proper authorization checks. Until then, consider disabling the plugin or implementing web application firewall rules to block manipulation of order-related URL parameters.

Recommended fix Moderate confidence

1.0.9 (or latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the OneClick Chat to Order plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. After updating, verify the plugin is running version 1.0.9 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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