CVE-2025-13142: CWE-352 Cross-Site Request Forgery (CSRF) in farvehandleren Custom Post Type
The Custom Post Type plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing nonce validation on the custom post type deletion functionality. This makes it possible for unauthenticated attackers to delete custom post types via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-13142 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the farvehandleren Custom Post Type plugin for WordPress, affecting all versions up to and including 1.0. The vulnerability stems from the absence of nonce validation on the custom post type deletion functionality. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without this validation, an attacker can craft a malicious request that, if executed by an authenticated site administrator (e.g., by clicking a link), results in the deletion of custom post types. This attack vector requires no authentication on the attacker’s part but depends on social engineering to induce administrator interaction. The vulnerability impacts the integrity of website content by allowing unauthorized deletion but does not affect confidentiality or availability. The CVSS 3.1 base score of 4.3 reflects the network attack vector, low complexity, no privileges required, but requiring user interaction and limited impact scope. No patches or known exploits are currently reported, but the risk remains significant for sites relying on this plugin for content management. The vulnerability is categorized under CWE-352, a common web security weakness related to CSRF attacks.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of WordPress-managed content. Unauthorized deletion of custom post types could disrupt business operations, damage brand reputation, and cause data loss, particularly for organizations relying heavily on WordPress for content publishing or e-commerce. Although the attack does not compromise sensitive data confidentiality or site availability, the loss or alteration of content can lead to operational downtime and require resource-intensive recovery efforts. Organizations with high administrative user counts or less stringent user training are more vulnerable to social engineering exploitation. Additionally, sectors such as media, education, and government that use WordPress extensively for public-facing content may face reputational damage if attackers exploit this vulnerability. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities once publicly disclosed.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they use the farvehandleren Custom Post Type plugin and update it once a patch is released. In the absence of an official patch, administrators can implement manual nonce validation on the deletion functionality by modifying the plugin code to include WordPress nonce checks. Additionally, organizations should enforce strict administrative access controls, limiting the number of users with deletion privileges and employing the principle of least privilege. User training is critical to reduce the risk of social engineering; administrators should be educated to recognize and avoid clicking suspicious links, especially those received via email or untrusted sources. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts can provide an additional layer of defense. Regular backups of WordPress content and database snapshots will facilitate recovery if unauthorized deletions occur. Monitoring administrative actions and enabling logging can help detect anomalous behavior early.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-13142: CWE-352 Cross-Site Request Forgery (CSRF) in farvehandleren Custom Post Type
Description
The Custom Post Type plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing nonce validation on the custom post type deletion functionality. This makes it possible for unauthenticated attackers to delete custom post types via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Technical Analysis
CVE-2025-13142 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the farvehandleren Custom Post Type plugin for WordPress, affecting all versions up to and including 1.0. The vulnerability stems from the absence of nonce validation on the custom post type deletion functionality. Nonces in WordPress are security tokens used to verify that requests originate from legitimate users and not from malicious third parties. Without this validation, an attacker can craft a malicious request that, if executed by an authenticated site administrator (e.g., by clicking a link), results in the deletion of custom post types. This attack vector requires no authentication on the attacker’s part but depends on social engineering to induce administrator interaction. The vulnerability impacts the integrity of website content by allowing unauthorized deletion but does not affect confidentiality or availability. The CVSS 3.1 base score of 4.3 reflects the network attack vector, low complexity, no privileges required, but requiring user interaction and limited impact scope. No patches or known exploits are currently reported, but the risk remains significant for sites relying on this plugin for content management. The vulnerability is categorized under CWE-352, a common web security weakness related to CSRF attacks.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of WordPress-managed content. Unauthorized deletion of custom post types could disrupt business operations, damage brand reputation, and cause data loss, particularly for organizations relying heavily on WordPress for content publishing or e-commerce. Although the attack does not compromise sensitive data confidentiality or site availability, the loss or alteration of content can lead to operational downtime and require resource-intensive recovery efforts. Organizations with high administrative user counts or less stringent user training are more vulnerable to social engineering exploitation. Additionally, sectors such as media, education, and government that use WordPress extensively for public-facing content may face reputational damage if attackers exploit this vulnerability. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities once publicly disclosed.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they use the farvehandleren Custom Post Type plugin and update it once a patch is released. In the absence of an official patch, administrators can implement manual nonce validation on the deletion functionality by modifying the plugin code to include WordPress nonce checks. Additionally, organizations should enforce strict administrative access controls, limiting the number of users with deletion privileges and employing the principle of least privilege. User training is critical to reduce the risk of social engineering; administrators should be educated to recognize and avoid clicking suspicious links, especially those received via email or untrusted sources. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts can provide an additional layer of defense. Regular backups of WordPress content and database snapshots will facilitate recovery if unauthorized deletions occur. Monitoring administrative actions and enabling logging can help detect anomalous behavior early.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-13T18:55:14.976Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6920235bcf2d47c38997b552
Added to database: 11/21/2025, 8:31:23 AM
Last enriched: 11/28/2025, 9:30:02 AM
Last updated: 1/7/2026, 5:25:20 AM
Views: 80
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighCVE-2026-22162
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.