CVE-2026-4139: CWE-352 Cross-Site Request Forgery (CSRF) in chsxf mCatFilter
The mCatFilter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 0.5.2. This is due to the complete absence of nonce verification and capability checks in the compute_post() function, which processes settings updates. The compute_post() function is called in the plugin constructor on every page load via the plugins_loaded hook, and it directly processes $_POST data to modify plugin settings via update_option() without any CSRF token validation. This makes it possible for unauthenticated attackers to modify all plugin settings, including category exclusion rules, feed exclusion flags, and tag page exclusion flags, via a forged POST request, granted they can trick a site administrator into performing an action such as clicking a link.
AI Analysis
Technical Summary
CVE-2026-4139 describes a CSRF vulnerability in the mCatFilter WordPress plugin (versions up to 0.5.2). The compute_post() function, invoked on every page load via the plugins_loaded hook, processes $_POST data to update plugin settings without nonce or capability checks. This lack of CSRF token validation enables attackers to forge POST requests that modify plugin settings such as category exclusion rules and feed exclusion flags by tricking an administrator into performing an action like clicking a malicious link.
Potential Impact
An attacker can cause an authenticated administrator to unknowingly modify all plugin settings by exploiting the absence of CSRF protections. This can lead to unauthorized changes in category and feed exclusion rules, potentially affecting site content filtering behavior. There is no direct confidentiality or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should exercise caution when clicking links and consider disabling or removing the vulnerable plugin if possible. Implementing web application firewall (WAF) rules to block suspicious POST requests targeting the plugin's settings endpoint may provide temporary mitigation.
CVE-2026-4139: CWE-352 Cross-Site Request Forgery (CSRF) in chsxf mCatFilter
Description
The mCatFilter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 0.5.2. This is due to the complete absence of nonce verification and capability checks in the compute_post() function, which processes settings updates. The compute_post() function is called in the plugin constructor on every page load via the plugins_loaded hook, and it directly processes $_POST data to modify plugin settings via update_option() without any CSRF token validation. This makes it possible for unauthenticated attackers to modify all plugin settings, including category exclusion rules, feed exclusion flags, and tag page exclusion flags, via a forged POST request, granted they can trick a site administrator into performing an action such as clicking a link.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4139 describes a CSRF vulnerability in the mCatFilter WordPress plugin (versions up to 0.5.2). The compute_post() function, invoked on every page load via the plugins_loaded hook, processes $_POST data to update plugin settings without nonce or capability checks. This lack of CSRF token validation enables attackers to forge POST requests that modify plugin settings such as category exclusion rules and feed exclusion flags by tricking an administrator into performing an action like clicking a malicious link.
Potential Impact
An attacker can cause an authenticated administrator to unknowingly modify all plugin settings by exploiting the absence of CSRF protections. This can lead to unauthorized changes in category and feed exclusion rules, potentially affecting site content filtering behavior. There is no direct confidentiality or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should exercise caution when clicking links and consider disabling or removing the vulnerable plugin if possible. Implementing web application firewall (WAF) rules to block suspicious POST requests targeting the plugin's settings endpoint may provide temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-13T15:29:31.027Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8877019fe3cd2cd808ff2
Added to database: 4/22/2026, 8:31:44 AM
Last enriched: 4/22/2026, 8:47:56 AM
Last updated: 4/23/2026, 3:26:43 AM
Views: 7
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.