{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12995 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12995 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12995 is a medium-severity missing authorization vulnerability in hiroaki-miyashita Custom Field Template, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12995 and fix it if it is affected.\n\nWhat it is: CVE-2026-12995 is a medium-severity missing authorization vulnerability in hiroaki-miyashita Custom Field Template, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12995 in the wild and no public exploit code.\n\nAffected product: hiroaki-miyashita Custom Field Template. 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-12995/ (Markdown: https://insights.sbomify.com/CVE-2026-12995/index.md)","id":"CVE-2026-12995","markdown":"https://insights.sbomify.com/CVE-2026-12995/index.md","name":"CVE-2026-12995","record":{"aliases":["GHSA-82h9-w9pg-f542"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can delete arbitrary media files via IDOR in Custom Field Template plugin, causing content loss.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The Custom Field Template plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.7.8 via the edit_meta_value due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary media attachments site-wide by supplying any numeric attachment ID in the file-field parameter alongside the corresponding delete flag, causing content loss and broken pages. Exploitation requires that the attacker's post is governed by a Custom Field Template containing at least one file-type field with the mediaRemove option not enabled, which is the default configuration for file fields.","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":"Missing authorization in Custom Field Template","id":"CVE-2026-12995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Use after free in OpenVPN","id":"CVE-2026-12996"},"packages":[],"prev":{"headline":"Missing authorization in WCFM – Frontend Manager for WooCommerce","id":"CVE-2026-12994"},"products":["Custom Field Template"],"published":"2026-09-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-09-22","vendors":["hiroaki-miyashita"]},"summary":"Authenticated contributors can delete arbitrary media files via IDOR in Custom Field Template plugin, causing content loss.","url":"https://insights.sbomify.com/CVE-2026-12995/"}