{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24918 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24918 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24918 is a medium-severity cross-site scripting vulnerability in Unknown Smash Balloon Social Post Feed, published on 29 Nov 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-24918 and fix it if it is affected.\n\nWhat it is: CVE-2021-24918 is a medium-severity cross-site scripting vulnerability in Unknown Smash Balloon Social Post Feed, published on 29 Nov 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-24918 in the wild and no public exploit code.\n\nAffected product: Unknown Smash Balloon Social Post Feed. 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-2021-24918/ (Markdown: https://insights.sbomify.com/CVE-2021-24918/index.md)","id":"CVE-2021-24918","markdown":"https://insights.sbomify.com/CVE-2021-24918/index.md","name":"CVE-2021-24918","record":{"aliases":["GHSA-j9qp-w82r-g5cf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Logged-in users can inject malicious JavaScript into plugin settings, leading to stored XSS attacks on site posts and pages.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"smash_balloon_social_post_feed","vendor":"smashballoon"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 Smash Balloon Social Post Feed WordPress plugin before 4.0.1 did not have any privilege or nonce validation before saving the plugin's setting. As a result, any logged-in user on a vulnerable site could update the settings and store rogue JavaScript on each of its posts and pages.","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":"Smash Balloon Social Post Feed \u003c 4.0.1 - Subscriber+ Arbitrary Plugin Settings Update to Stored XSS","id":"CVE-2021-24918","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Wicked Folders \u003c 2.18.10 - Subscriber+ SQL Injection","id":"CVE-2021-24919"},"packages":[],"prev":{"headline":"WPS Hide Login \u003c 1.9.1 - Protection Bypass with Referer-Header","id":"CVE-2021-24917"},"products":["Smash Balloon Social Post Feed"],"published":"2021-11-29","related":[{"cvss_score":6.1,"headline":"Smash Balloon Social Post Feed \u003c 2.19.2 - Unauthenticated Stored XSS","id":"CVE-2021-24508","kev_date_added":null,"published":"2021-09-13"},{"cvss_score":5.4,"headline":"Smash Balloon Social Post Feed \u003c 4.1.6 - Contributor+ Stored XSS","id":"CVE-2022-4477","kev_date_added":null,"published":"2023-01-16"},{"cvss_score":5.4,"headline":"Smash Balloon Social Post Feed \u003c 4.1.1 - Authenticated Reflected Cross-Site Scripting (XSS)","id":"CVE-2021-25065","kev_date_added":null,"published":"2022-01-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Logged-in users can inject malicious JavaScript into plugin settings, leading to stored XSS attacks on site posts and pages.","url":"https://insights.sbomify.com/CVE-2021-24918/"}