{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4139 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4139 is a medium-severity vulnerability in chsxf mCatFilter, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-4139 and fix it if it is affected.\n\nWhat it is: CVE-2026-4139 is a medium-severity vulnerability in chsxf mCatFilter, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-4139 in the wild and no public exploit code.\n\nAffected product: chsxf mCatFilter. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4139/ (Markdown: https://insights.sbomify.com/CVE-2026-4139/index.md)","id":"CVE-2026-4139","markdown":"https://insights.sbomify.com/CVE-2026-4139/index.md","name":"CVE-2026-4139","record":{"aliases":["GHSA-9p67-72c6-m54h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify plugin settings via CSRF if an administrator clicks a malicious link.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"mCatFilter \u003c= 0.5.2 - Cross-Site Request Forgery via compute_post() Function","id":"CVE-2026-4139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site request forgery in Ni WooCommerce Order Export","id":"CVE-2026-4140"},"packages":[],"prev":{"headline":"DX Unanswered Comments \u003c= 1.7 - Cross-Site Request Forgery via Settings Update","id":"CVE-2026-4138"},"products":["mCatFilter"],"published":"2026-04-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["chsxf"]},"summary":"Unauthenticated attackers can modify plugin settings via CSRF if an administrator clicks a malicious link.","url":"https://insights.sbomify.com/CVE-2026-4139/"}