{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8239 exists.","fix":"No fix has been published for CVE-2024-8239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8239 is a medium-severity cross-site scripting vulnerability in Unknown Starbox, published on 30 Sep 2024. 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-2024-8239 and fix it if it is affected.\n\nWhat it is: CVE-2024-8239 is a medium-severity cross-site scripting vulnerability in Unknown Starbox, published on 30 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8239 exists.\n\nAffected product: Unknown Starbox. 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-8239/ (Markdown: https://insights.sbomify.com/CVE-2024-8239/index.md)","id":"CVE-2024-8239","markdown":"https://insights.sbomify.com/CVE-2024-8239/index.md","name":"CVE-2024-8239","record":{"aliases":["GHSA-f25r-g5v8-v6qj"],"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":"Contributors can inject malicious scripts via social media profile URLs in the Starbox WordPress plugin, leading to stored XSS attacks.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"starbox","vendor":"squirrly"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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 Starbox  WordPress plugin before 3.5.3 does not properly render social media profiles URLs in certain contexts, like the malicious user's profile or pages where the starbox shortcode is used, which may be abused by users with at least the contributor role to conduct Stored XSS attacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Starbox \u003c 3.5.3 - Contributor+ Stored XSS","id":"CVE-2024-8239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-8240"},"packages":[],"prev":{"headline":"Unrestricted Code Execution in aimhubio/aim","id":"CVE-2024-8238"},"products":["Starbox"],"published":"2024-09-30","related":[{"cvss_score":6.4,"headline":"Starbox \u003c= 3.4.8 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Job Settings","id":"CVE-2023-6806","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":6.4,"headline":"Starbox \u003c= 3.4.8 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Profile Display Name and Social Settings","id":"CVE-2024-0256","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":6.1,"headline":"Starbox \u003c 3.5.0 - Contributor+ Stored XSS","id":"CVE-2024-1273","kev_date_added":null,"published":"2024-03-11"},{"cvss_score":4.8,"headline":"Starbox \u003c 3.5.2 - Admin+ Stored XSS","id":"CVE-2024-7955","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":4.3,"headline":"Starbox – the Author Box for Humans \u003c= 3.4.7 - Insecure Direct Object Reference","id":"CVE-2024-0366","kev_date_added":null,"published":"2024-02-05"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-01","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via social media profile URLs in the Starbox WordPress plugin, leading to stored XSS attacks.","url":"https://insights.sbomify.com/CVE-2024-8239/"}