Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-60139: CWE-352 Cross-Site Request Forgery (CSRF) in Joovii Sendle Shipping

0
Medium
VulnerabilityCVE-2025-60139cvecve-2025-60139cwe-352
Published: Fri Sep 26 2025 (09/26/2025, 08:31:45 UTC)
Source: CVE Database V5
Vendor/Project: Joovii
Product: Sendle Shipping

Description

Cross-Site Request Forgery (CSRF) vulnerability in Joovii Sendle Shipping allows Cross Site Request Forgery. This issue affects Sendle Shipping: from n/a through 6.02.

AI-Powered Analysis

AILast updated: 09/27/2025, 00:10:49 UTC

Technical Analysis

CVE-2025-60139 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Joovii Sendle Shipping plugin, affecting versions up to 6.02. CSRF vulnerabilities allow an attacker to trick an authenticated user into submitting unwanted actions on a web application in which they are currently authenticated. In this case, the vulnerability arises because the Sendle Shipping plugin does not adequately verify the origin of requests, enabling attackers to craft malicious requests that could be executed with the privileges of the authenticated user. The CVSS 3.1 base score of 4.3 reflects a medium severity, indicating that while the vulnerability does not impact confidentiality or availability, it can affect the integrity of the application by allowing unauthorized state-changing actions. The attack vector is network-based (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R), such as clicking a malicious link or visiting a crafted webpage. The scope remains unchanged (S:U), meaning the vulnerability affects only the vulnerable component without impacting other components. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability is classified under CWE-352, which is a common web security weakness related to CSRF attacks. Since Sendle Shipping is a plugin likely used in e-commerce or shipping management contexts, exploitation could allow attackers to manipulate shipping orders or configurations without authorization, potentially leading to fraudulent shipments or disruption of logistics workflows.

Potential Impact

For European organizations, especially those engaged in e-commerce, logistics, or shipping operations using the Joovii Sendle Shipping plugin, this vulnerability poses a risk of unauthorized manipulation of shipping orders or configurations. While the vulnerability does not directly compromise sensitive data confidentiality or system availability, it can undermine the integrity of shipping processes, leading to financial losses, reputational damage, and operational disruptions. Attackers could exploit this vulnerability to create fraudulent shipments, alter delivery details, or disrupt order fulfillment, which can be particularly damaging in highly regulated markets with strict compliance requirements such as GDPR. Additionally, the medium severity and requirement for user interaction mean that phishing or social engineering campaigns could be used to trigger the exploit, increasing the risk in environments where users have elevated privileges or access to critical shipping functions. The lack of known exploits currently reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Immediately monitor for updates or patches from Joovii for the Sendle Shipping plugin and apply them as soon as they become available. 2) Implement anti-CSRF tokens in all forms and state-changing requests within the shipping management system to ensure that requests are validated for authenticity. 3) Enforce strict SameSite cookie attributes to reduce the risk of CSRF attacks via cross-origin requests. 4) Educate users, especially those with access to shipping management interfaces, about the risks of phishing and social engineering attacks that could trigger CSRF exploits. 5) Restrict user privileges to the minimum necessary, limiting the ability of compromised accounts to perform critical shipping actions. 6) Employ web application firewalls (WAFs) with rules designed to detect and block CSRF attack patterns. 7) Conduct regular security assessments and penetration testing focused on web application vulnerabilities, including CSRF, to identify and remediate weaknesses proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:27:39.207Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d72b6079aa5c9d0854f440

Added to database: 9/27/2025, 12:10:08 AM

Last enriched: 9/27/2025, 12:10:49 AM

Last updated: 10/7/2025, 1:41:26 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats