Sendle Shipping CVE-2025-62976
MEDIUMSeverity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Network-reachable endpoint with no auth required; impact is availability-only per described functionality disruption, no data exposure or integrity change.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
1DescriptionCVE.org
Missing Authorization vulnerability in Joovii Sendle Shipping official-sendle-shipping-method allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Sendle Shipping: from n/a through <= 6.02.
AnalysisAI
Broken access control in the Sendle Shipping WordPress plugin (official-sendle-shipping-method) versions through 6.02 allows unauthenticated remote attackers to invoke plugin functionality that should be restricted to authorized users. The flaw stems from missing authorization checks (CWE-862), meaning certain shipping-related actions are accessible without any privilege verification. Real-world impact is limited to availability disruption (CVSS A:L), with no confidentiality or integrity impact identified. No public exploit code exists and EPSS places exploitation probability at 0.04% (11th percentile), indicating negligible active threat at time of analysis.
Technical ContextAI
The vulnerability resides in the Joovii-developed Sendle Shipping plugin for WordPress (CPE: wordpress plugin official-sendle-shipping-method ≤ 6.02). CWE-862 (Missing Authorization) describes a pattern where the application fails to verify that the requesting user holds the required permission before executing a privileged operation - distinct from CWE-287 (authentication failure) in that the user's identity may be unverified entirely. In WordPress, this class of flaw typically manifests as AJAX handlers, REST API endpoints, or admin-page callbacks registered without a capability check (e.g., missing check_ajax_referer(), current_user_can(), or equivalent). The CVSS vector AV:N/AC:L/PR:N/UI:N confirms the vulnerable endpoint is network-reachable and requires no prior authentication or complex preconditions. The 'Authentication Bypass' tag from Patchstack aligns with this - certain plugin operations are reachable without credential verification. Impact is scoped to availability (A:L), suggesting the exposed functionality can disrupt the plugin's operation (e.g., resetting shipping rate data, triggering erroneous API calls to Sendle's carrier API) without leaking data or altering persistent records.
Affected ProductsAI
The Sendle Shipping WordPress plugin by Joovii, published under the slug 'official-sendle-shipping-method', is affected in all versions from the initial release through and including version 6.02. No lower version bound is specified, suggesting all historical releases are vulnerable. The vulnerability is documented by Patchstack at https://patchstack.com/database/Wordpress/Plugin/official-sendle-shipping-method/vulnerability/wordpress-sendle-shipping-plugin-6-02-broken-access-control-vulnerability. No vendor advisory from Joovii is available in the provided intelligence; affected version range is sourced from NVD and Patchstack reporting only.
RemediationAI
The primary remediation is to update the Sendle Shipping plugin beyond version 6.02 to any release that addresses the missing authorization check. As of the time of this analysis, no specific patched version number has been confirmed by the vendor or independently verified - the Patchstack advisory (https://patchstack.com/database/Wordpress/Plugin/official-sendle-shipping-method/vulnerability/wordpress-sendle-shipping-plugin-6-02-broken-access-control-vulnerability) should be monitored for a confirmed fix version. If an updated plugin version is unavailable, WordPress site administrators should consider temporarily deactivating the Sendle Shipping plugin to eliminate the attack surface - the trade-off is loss of Sendle carrier rate calculation at checkout. Alternatively, a Web Application Firewall (WAF) rule blocking unauthenticated requests to the plugin's specific AJAX or REST endpoints can serve as a compensating control; however, the specific endpoint paths are not confirmed in available data, so WAF implementation requires code-level inspection of the plugin. Restrict WordPress admin panel access to trusted IP ranges as a defense-in-depth measure. Given the low severity and availability-only impact, risk acceptance with monitoring may be appropriate for sites where plugin deactivation is not feasible.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today