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

CVE-2026-57341

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

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
Unauthenticated Insecure Direct Object References (IDOR) in Colissimo Officiel : Méthodes de livraison pour WooCommerce <= 2.9.0 versions.

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

Unauthenticated IDOR vulnerability in the Colissimo Officiel WooCommerce shipping plugin versions 2.9.0 and earlier allows unauthenticated attackers to access or modify sensitive objects (likely shipping data, orders, or configuration) without proper authorization validation due to missing or inadequate object-level access controls.

MitigationUpgrade the Colissimo Officiel plugin to a version newer than 2.9.0, or if no patched version is available, disable the plugin until a security update is released.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 Colissimo Officiel plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Colissimo Officiel' in the list, or inspect the plugin directory /wp-content/plugins/ for a folder containing 'colissimo' in the name
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click 'View Details' on Colissimo Officiel or open the main plugin PHP file and locate the 'Version:' header comment
    Affected if Version field shows 2.9.0 or any version number lower than 2.9.0
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Colissimo Officiel row shows 'Activate' is not present and the plugin is loaded
    Affected if Plugin status shows as Active (not deactivated or deleted)
  4. Test unauthenticated access to plugin endpoints
    Send a crafted GET or POST request to common plugin AJAX handlers such as /wp-admin/admin-ajax.php?action=colissimo_ followed by an operation, or /wp-json/colissimo/v1/ endpoints, without providing any authentication cookies or headers
    Affected if The server returns HTTP 200 with order, shipping, or configuration data instead of requiring login or returning HTTP 401/403

Your environment is affected if the Colissimo Officiel WooCommerce plugin version 2.9.0 or earlier is installed and active, and plugin endpoints are 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Colissimo Officiel plugin to a version newer than 2.9.0, or if no patched version is available, disable the plugin until a security update is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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