{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-7388 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-7388 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-7388 is a medium-severity cross-site scripting vulnerability in gfazioli WP Bannerize Pro, published on 13 Aug 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-7388 and fix it if it is affected.\n\nWhat it is: CVE-2024-7388 is a medium-severity cross-site scripting vulnerability in gfazioli WP Bannerize Pro, published on 13 Aug 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-7388 in the wild and no public exploit code.\n\nAffected product: gfazioli WP Bannerize Pro. 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-2024-7388/ (Markdown: https://insights.sbomify.com/CVE-2024-7388/index.md)","id":"CVE-2024-7388","markdown":"https://insights.sbomify.com/CVE-2024-7388/index.md","name":"CVE-2024-7388","record":{"aliases":["GHSA-c6cg-7q2c-x256"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated editors can inject arbitrary scripts via banner alt data in WP Bannerize Pro, affecting multi-site or restricted HTML installations.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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 WP Bannerize Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via banner alt data in all versions up to, and including, 1.9.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.","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":"WP Bannerize Pro \u003c= 1.9.0 - Authenticated (Editor+) Stored Cross-Site Scripting","id":"CVE-2024-7388","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Forminator \u003c= 1.29.1 - HubSpot Developer API Key Sensitive Information Exposure","id":"CVE-2024-7389"},"packages":[],"prev":{"headline":"Openshift/builder: path traversal allows command injection in privileged buildcontainer using docker build strategy","id":"CVE-2024-7387"},"products":["WP Bannerize Pro"],"published":"2024-08-13","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":["gfazioli"]},"summary":"Authenticated editors can inject arbitrary scripts via banner alt data in WP Bannerize Pro, affecting multi-site or restricted HTML installations.","url":"https://insights.sbomify.com/CVE-2024-7388/"}