dbcve.org
VulnerabilityAwaiting classification

CVE-2026-9702

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
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 InPost PL WordPress plugin before 1.9.1 does not verify that the request originates from the legitimate buyer before allowing the WooCommerce order parcel-locker destination to be updated, allowing unauthenticated attackers to silently redirect the shipping destination of any pending or processing order on the 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 InPost PL WordPress plugin before version 1.9.1 lacks proper authorization checks on the parcel-locker destination update functionality, allowing unauthenticated attackers to modify shipping destinations of any pending or processing WooCommerce order. This is a broken access control vulnerability where the plugin fails to verify the request originates from the legitimate buyer.

MitigationUpdate the InPost PL plugin to version 1.9.1 or later. Additionally, implement proper authentication and authorization checks (e.g., verify user session, add nonce validation) before allowing order destination modifications.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check InPost PL plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'InPost PL' (or InPost Paczkomaty). The version number is displayed below the plugin name. Alternatively, check the plugin file header in /wp-content/plugins/inpost-pl/inpost-pl.php for 'Version:' tag.
    Affected if Version is lower than 1.9.1 (e.g., 1.9.0, 1.8.x, etc.)
  2. Verify WooCommerce is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm WooCommerce is installed and active. This plugin extends WooCommerce shipping functionality.
    Affected if WooCommerce is not installed or not active - the vulnerability only affects WooCommerce order shipping destinations
  3. Check for pending or processing orders using parcel locker shipping
    In WordPress admin, go to WooCommerce > Orders. Look for orders with status 'Pending payment' or 'Processing' and check the shipping method - look for 'InPost', 'Paczkomaty', or 'parcel locker' in the shipping details.
    Affected if There are pending or processing orders that use InPost parcel locker shipping - these are the orders that could be tampered with
  4. Test parcel locker destination update endpoint accessibility
    If you have access to server logs or can make a test request, examine the AJAX endpoint or REST API route used by the plugin for parcel locker updates (typically involves 'inpost' or 'parcellocker' in the URL). Attempt a request without authentication credentials to see if it is accepted.
    Affected if The endpoint accepts unauthenticated requests and processes parcel locker destination updates without requiring user verification

You are affected if the InPost PL plugin version is below 1.9.1, WooCommerce is active, and there are pending/processing orders using InPost parcel locker shipping that could be modified by unauthenticated users.

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 InPost PL plugin to version 1.9.1 or later. Additionally, implement proper authentication and authorization checks (e.g., verify user session, add nonce validation) before allowing order destination modifications.

Recommended fix Moderate confidence

InPost PL plugin version 1.9.1 or later

  1. Create a full backup of the WordPress site before making any changes
  2. Update the InPost PL WordPress plugin to version 1.9.1 or later through the WordPress admin dashboard (Plugins > Available Plugins > Update Now)
  3. Alternatively, upload and install version 1.9.1 or later manually via Plugins > Add New > Upload Plugin
  4. Verify the update completed successfully by checking the plugin version in the installed plugins list
  5. Test that legitimate customers can still set parcel locker destinations on WooCommerce orders without issues
  6. Confirm the site is functioning normally after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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