{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4068 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4068 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4068 is a medium-severity vulnerability in pattihis Add Custom Fields to Media, published on 19 Mar 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-4068 and fix it if it is affected.\n\nWhat it is: CVE-2026-4068 is a medium-severity vulnerability in pattihis Add Custom Fields to Media, published on 19 Mar 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-4068 in the wild and no public exploit code.\n\nAffected product: pattihis Add Custom Fields to Media. 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-4068/ (Markdown: https://insights.sbomify.com/CVE-2026-4068/index.md)","id":"CVE-2026-4068","markdown":"https://insights.sbomify.com/CVE-2026-4068/index.md","name":"CVE-2026-4068","record":{"aliases":["GHSA-v95j-rfx2-j67m"],"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":"Attackers can trick administrators into deleting custom media fields via CSRF due to missing nonce validation in the Add Custom Fields to Media plugin.","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 Add Custom Fields to Media plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.3. This is due to missing nonce validation on the field deletion functionality in the admin display template. The plugin properly validates a nonce for the 'add field' operation (line 24-36), but the 'delete field' operation (lines 38-49) processes the $_GET['delete'] parameter and calls update_option() without any nonce verification. This makes it possible for unauthenticated attackers to delete arbitrary custom media fields via a forged request, granted they can trick a site administrator into performing an action such as clicking on 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":"Add Custom Fields to Media \u003c= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter","id":"CVE-2026-4068","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Alfie – Feed Plugin \u003c= 1.2.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'naam' Parameter","id":"CVE-2026-4069"},"packages":[],"prev":{"headline":"Ad Short \u003c= 2.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'client' Shortcode Attribute","id":"CVE-2026-4067"},"products":["Add Custom Fields to Media"],"published":"2026-03-19","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-08","vendors":["pattihis"]},"summary":"Attackers can trick administrators into deleting custom media fields via CSRF due to missing nonce validation in the Add Custom Fields to Media plugin.","url":"https://insights.sbomify.com/CVE-2026-4068/"}