{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6526 is a medium-severity cross-site scripting vulnerability in metabox Meta Box, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-6526 and fix it if it is affected.\n\nWhat it is: CVE-2023-6526 is a medium-severity cross-site scripting vulnerability in metabox Meta Box, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-6526 in the wild and no public exploit code.\n\nAffected product: metabox Meta Box. 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-2023-6526/ (Markdown: https://insights.sbomify.com/CVE-2023-6526/index.md)","id":"CVE-2023-6526","markdown":"https://insights.sbomify.com/CVE-2023-6526/index.md","name":"CVE-2023-6526","record":{"aliases":["GHSA-vj7x-j42w-v27g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject arbitrary scripts via custom post meta values, leading to stored XSS execution for other users.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"meta_box","vendor":"metabox"}],"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 Meta Box – WordPress Custom Fields Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom post meta values displayed through the plugin's shortcode in all versions up to, and including, 5.9.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","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":"Meta Box – WordPress Custom Fields Framework \u003c= 5.9.2 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2023-6526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Email Subscription Popup \u003c= 1.2.18 - Reflected Cross-Site Scripting","id":"CVE-2023-6527"},"packages":[],"prev":{"headline":"ElementsKit Elementor addons \u003c= 3.0.3 - Authenticated(Editor+) Stored Cross-Site Scripting","id":"CVE-2023-6525"},"products":["Meta Box"],"published":"2024-02-05","related":[{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2019-14794","kev_date_added":null,"published":"2019-08-09"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2019-14793","kev_date_added":null,"published":"2019-08-09"},{"cvss_score":4.3,"headline":"Meta Box \u003c 5.9.4 - Contributor+ Arbitrary Posts' Custom Field Disclosure","id":"CVE-2024-1204","kev_date_added":null,"published":"2024-04-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":["metabox"]},"summary":"Authenticated contributors can inject arbitrary scripts via custom post meta values, leading to stored XSS execution for other users.","url":"https://insights.sbomify.com/CVE-2023-6526/"}