{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-29022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29022 is a high-severity cross-site scripting vulnerability in xibosignage xibo-cms, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-29022 and fix it if it is affected.\n\nWhat it is: CVE-2024-29022 is a high-severity cross-site scripting vulnerability in xibosignage xibo-cms, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-29022 in the wild and no public exploit code.\n\nAffected product: xibosignage xibo-cms. 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-29022/ (Markdown: https://insights.sbomify.com/CVE-2024-29022/index.md)","id":"CVE-2024-29022","markdown":"https://insights.sbomify.com/CVE-2024-29022/index.md","name":"CVE-2024-29022","record":{"aliases":["GHSA-xchw-pf2w-rpgq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Xibo CMS","requires_auth":"none","summary":"Attackers can inject scripts via unsanitized headers to steal session IDs and hijack user sessions in Xibo CMS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"Xibo is an Open Source Digital Signage platform with a web content management system and Windows display player software. In affected versions some request headers are not correctly sanitised when stored in the session and display tables. These headers can be used to inject a malicious script into the session page to exfiltrate session IDs and User Agents. These session IDs / User Agents can subsequently be used to hijack active sessions. A malicious script can be injected into the display grid to exfiltrate information related to displays. Users should upgrade to version 3.3.10 or 4.0.9 which fix this issue. Customers who host their CMS with the Xibo Signage service have already received an upgrade or patch to resolve this issue regardless of the CMS version that they are running. Upgrading to a fixed version is necessary to remediate. Patches are available for earlier versions of Xibo CMS that are out of security support: 2.3 patch ebeccd000b51f00b9a25f56a2f252d6812ebf850.diff. 1.8 patch a81044e6ccdd92cc967e34c125bd8162432e51bc.diff. There are no known workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Session Hijacking via XSS attack in header and session grid in Xibo CMS","id":"CVE-2024-29022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Session Hijacking via token exposure on the session page in Xibo CMS","id":"CVE-2024-29023"},"packages":[],"prev":{"headline":"SSRF into Sandbox Escape through Unsafe Default Configuration","id":"CVE-2024-29021"},"products":["xibo-cms"],"published":"2024-04-12","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":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["xibosignage"]},"summary":"Attackers can inject scripts via unsanitized headers to steal session IDs and hijack user sessions in Xibo CMS.","url":"https://insights.sbomify.com/CVE-2024-29022/"}