Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach admin-ajax.php unauthenticated
-
ExploitInvoke unprotected nopriv AJAX action
-
ExecutionSupply arbitrary order IDs
-
ImpactDelete shipment records and trigger carrier waybill deletion
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special configuration is required beyond having the Shipping for Nova Poshta plugin (version 1.19.8 or earlier) installed and active with its Nova Poshta API credentials stored, which is the normal operating state - the vulnerable AJAX action is explicitly exposed to unauthenticated (nopriv) users with no authorization, nonce, or ownership validation. The main practical limiter is that the attacker must reference target order identifiers to affect specific orders (arbitrary/other orders are reachable, but may require ID enumeration or guessing); there is no authentication, user-interaction, or non-default-setting barrier. Exploitation is confined to stores running this specific plugin, which bounds real-world exposure. |
| Impact | This is a genuine but moderate-severity broken-access-control flaw, not a high-urgency emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3) is internally consistent with the description: a remote, unauthenticated attacker can reach a vulnerable AJAX action over the network with low complexity and no user interaction, producing a limited integrity impact (destruction of shipment records and triggering waybill-deletion). A public exploit exists (WPScan), which raises practical risk, but there is NO CISA KEV listing and NO EPSS score was supplied, so there is no evidence of active, widespread exploitation - exploit availability and active exploitation are distinct signals and only the former is present here. No SSVC decision data was provided. The impact is bounded: C:N means no data is exposed, and A:N means the carrier/site stays up; the harm is tampering with/deleting order shipment data and causing unwanted carrier-side waybill deletions using the store's stored API credentials. Net: a real priority for stores actually running this plugin (unauthenticated + public PoC), but the limited integrity-only impact and regional niche footprint keep it below critical-patch-now status. One flag: the 'Information Disclosure' tag conflicts with the CVSS vector (C:N) and the description, which describe data destruction/tampering, not disclosure - treat the tag as mislabeled. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted AJAX request (wp-admin/admin-ajax.php) to the plugin's unprotected nopriv action, specifying order identifiers they do not own. Because no authorization, nonce, or ownership check is performed, the store deletes those orders' shipment records and issues waybill-deletion requests to Nova Poshta using the store's own stored API credentials. A public proof-of-concept is available via WPScan, lowering the skill required to reproduce this. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Unauthenticated attackers can permanently delete shipment records belonging to arbitrary orders on WordPress sites running the Shipping for Nova Poshta plugin through version 1.19.8, and can additionally cause the store to fire the carrier's waybill-deletion request using the store's own stored Nova Poshta API credentials. The vulnerable AJAX action is registered for unauthenticated users and performs no authorization, nonce, or ownership validation, so no login, user interaction, or non-default configuration is required - the only friction is that the attacker must supply a target order identifier, which may require enumeration. Publicly available exploit code exists (reported via WPScan); there is no confirmation of active exploitation (not in CISA KEV), and the practical exposure is bounded to stores that have this specific plugin installed and active.
RemediationAI
No vendor-released patch is identified at time of analysis for the Shipping for Nova Poshta plugin through 1.19.8, so the primary action is to deactivate and remove the plugin until the vendor publishes a fixed version, accepting the loss of Nova Poshta shipping/waybill functionality as the trade-off. If deactivation is not operationally possible, apply compensating controls at the edge: block unauthenticated POST requests to /wp-admin/admin-ajax.php that carry the plugin's vulnerable action parameter (a targeted WAF or reverse-proxy rule risks false positives only if written broadly against all admin-ajax traffic, so scope it to the specific action name), and remove the stored Nova Poshta API credentials from the plugin settings to prevent the store from issuing carrier waybill-deletion requests on the attacker's behalf - with the side effect that legitimate shipment and waybill generation stops until credentials are restored. Additionally, monitor order and shipment metadata for unexpected deletions, keep full-site backups so deleted shipment records can be restored, and re-check https://wpscan.com/vulnerability/e1ba1fbc-f61f-446f-a312-d725364313a6/ periodically for a vendor fix. Note that the vulnerable endpoint is unauthenticated by design, so no credential rotation or role restriction on the WordPress side mitigates it.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in a WordPress plugin AJAX handler that is exposed to unauthenticated visitors, typically via a wp_ajax_nopriv_* action hook, and that handler lacks the trio of controls WordPress plugins are expected to enforce: a capability check (current_user_can), a CSRF nonce check (check_ajax_referer/wp_verify_nonce), and an ownership/authorization check that the submitted order actually belongs to the caller. Because the handler is reachable through wp-admin/admin-ajax.php and no server-side validation is performed, any remote client that can craft the expected request can manipulate the plugin's shipment records and trigger its Nova Poshta API integration. The source data assigns no CWE identifier, but the root cause is unambiguously the missing-authorization class (CWE-862, Missing Authorization); the CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N reflects network reachability with no privileges or user interaction, and an integrity-only impact (record deletion and an outbound waybill-deletion API call) rather than confidentiality or availability loss. The affected CPE string is cpe:2.3:a:unknown:shipping_for_nova_poshta:*:*:*:*:*:*:*:*, with the vendor field recorded as unknown, so version-range qualification comes from the vendor advisory (through 1.19.8) rather than from the CPE dictionary.
Know when Shipping For Nova Poshta gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Unauthenticated nopriv AJAX over the network gives AV:N/AC:L/PR:N/UI:N; destroying shipment records and forcing waybill deletion is a limited integrity impact (I:L), with no data disclosure (C:N) and no system outage (A:N).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
DescriptionCVE.org
The Shipping for Nova Poshta WordPress plugin through 1.19.8 does not perform any authorisation, nonce or ownership checks on one of its AJAX actions available to unauthenticated users, allowing anyone to delete the shipment records of arbitrary orders and to make the store issue the carrier's waybill-deletion request for those orders using the store's own stored API credentials.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-95707
GHSA-gvw5-gchw-rwg7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB