Skip to main content
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-12373: CWE-352 Cross-Site Request Forgery (CSRF) in torod Torod – The smart shipping and delivery portal for e-shops and retailers

0
Medium
VulnerabilityCVE-2025-12373cvecve-2025-12373cwe-352
Published: Fri Dec 05 2025 (12/05/2025, 06:07:18 UTC)
Source: CVE Database V5
Vendor/Project: torod
Product: Torod – The smart shipping and delivery portal for e-shops and retailers

Description

The Torod – The smart shipping and delivery portal for e-shops and retailers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9. This is due to missing or incorrect nonce validation on the save_settings function. This makes it possible for unauthenticated attackers to modify plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 20:25:49 UTC

Technical Analysis

CVE-2025-12373 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Torod WordPress plugin, a tool designed to facilitate smart shipping and delivery for e-commerce platforms and retailers. The vulnerability exists in all versions up to and including 1.9 due to the absence or improper implementation of nonce validation within the save_settings function. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and not from malicious sources. Without proper nonce validation, attackers can craft malicious requests that, when executed by an authenticated administrator (e.g., by clicking a link), cause unauthorized changes to the plugin’s settings. This attack vector does not require the attacker to be authenticated but does require user interaction from an administrator, making social engineering a key component of exploitation. The vulnerability primarily impacts the integrity of the plugin’s configuration, potentially leading to misconfigurations that could disrupt shipping or delivery processes or open further attack vectors. The CVSS v3.1 base score is 4.3, reflecting a medium severity level, with an attack vector of network, low attack complexity, no privileges required, and user interaction needed. Currently, there are no known exploits in the wild, and no patches have been linked yet, indicating that mitigation relies on vendor updates and best practices.

Potential Impact

The primary impact of this vulnerability is on the integrity of the affected system’s configuration. Unauthorized modification of shipping and delivery settings could disrupt e-commerce operations, potentially causing shipment delays, incorrect order processing, or exposure to further security risks if malicious configurations are introduced. While confidentiality and availability are not directly affected, the disruption to business processes can lead to financial losses, reputational damage, and operational inefficiencies. Since the attack requires an administrator’s interaction, the risk is somewhat mitigated by user awareness but remains significant in environments where administrators may be targeted by phishing or social engineering campaigns. Organizations relying on the Torod plugin for critical shipping workflows may face operational risks until the vulnerability is remediated.

Mitigation Recommendations

To mitigate this vulnerability, organizations should first monitor for updates from the Torod plugin vendor and apply patches as soon as they become available. In the absence of an official patch, administrators can implement manual nonce validation in the save_settings function to ensure requests are legitimate. Additionally, organizations should enforce strict administrative access controls and limit the number of users with plugin configuration privileges. Educating administrators about the risks of phishing and social engineering attacks is critical to prevent inadvertent exploitation. Employing web application firewalls (WAFs) with rules to detect and block suspicious CSRF attempts can provide an additional layer of defense. Regularly auditing plugin configurations and monitoring logs for unusual changes can help detect exploitation attempts early. Finally, consider isolating the WordPress administrative interface behind VPNs or IP whitelisting to reduce exposure.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-27T21:06:28.880Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69327c01f88dbe026c7c1597

Added to database: 12/5/2025, 6:30:25 AM

Last enriched: 2/27/2026, 8:25:49 PM

Last updated: 3/24/2026, 2:01:08 PM

Views: 113

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 require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses