{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-2305 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2305 is a medium-severity cross-site scripting vulnerability in AddFunc Head \u0026 Footer Code, published on 10 Apr 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-2305 and fix it if it is affected.\n\nWhat it is: CVE-2026-2305 is a medium-severity cross-site scripting vulnerability in AddFunc Head \u0026 Footer Code, published on 10 Apr 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-2305 in the wild and no public exploit code.\n\nAffected product: AddFunc Head \u0026 Footer Code. 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-2305/ (Markdown: https://insights.sbomify.com/CVE-2026-2305/index.md)","id":"CVE-2026-2305","markdown":"https://insights.sbomify.com/CVE-2026-2305/index.md","name":"CVE-2026-2305","record":{"aliases":["GHSA-5pcm-449r-xrg6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject malicious scripts via custom fields, leading to code execution when administrators view posts.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The AddFunc Head \u0026 Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `aFhfc_head_code`, `aFhfc_body_code`, and `aFhfc_footer_code` post meta values in all versions up to, and including, 2.3. This is due to the plugin outputting these meta values without any sanitization or escaping. While the plugin restricts its own metabox and save handler to administrators via `current_user_can('manage_options')`, it does not use `register_meta()` with an `auth_callback` to protect these meta keys. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts via the WordPress Custom Fields interface that execute when an administrator previews or views the post.","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":"AddFunc Head \u0026 Footer Code \u003c= 2.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Fields","id":"CVE-2026-2305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Ninja Tables \u003c= 5.2.6 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Table Creation","id":"CVE-2026-2306"},"packages":[],"prev":{"headline":"Heap Out-of-Bounds Read in Go Driver GSSAPI C Wrappers enables application crash or information leak","id":"CVE-2026-2303"},"products":["AddFunc Head \u0026 Footer Code"],"published":"2026-04-10","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-10","vendors":["addfunc"]},"summary":"Authenticated contributors can inject malicious scripts via custom fields, leading to code execution when administrators view posts.","url":"https://insights.sbomify.com/CVE-2026-2305/"}