{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66824 exists.","fix":"No fix has been published for CVE-2025-66824 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66824 is a high-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2025. 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-2025-66824 and fix it if it is affected.\n\nWhat it is: CVE-2025-66824 is a high-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2025. 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-2025-66824 exists.\n\nAffected product: n/a. 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-2025-66824/ (Markdown: https://insights.sbomify.com/CVE-2025-66824/index.md)","id":"CVE-2025-66824","markdown":"https://insights.sbomify.com/CVE-2025-66824/index.md","name":"CVE-2025-66824","record":{"aliases":["GHSA-wc9p-rvp2-mc4r"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TrueConf Server","requires_auth":"low_privilege","summary":"Attackers can inject scripts into the meeting location field to achieve full account takeover when victims view the conference info page.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trueconf_server","vendor":"trueconf"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A Stored Cross-Site Scripting (XSS) vulnerability exists in the Meeting location field of the Create/Edit Conference functionality in TrueConf Server v5.5.2.10813. The injected payload is stored via the meeting_room parameter and executed when users visit the Conference Info page, allowing attackers to achieve full Account Takeover (ATO). This issue is caused by improper sanitization of user-supplied input in the meeting_room field.","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":"Cross-site scripting in n/a","id":"CVE-2025-66824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2025-66834"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-66823"},"products":["n/a"],"published":"2025-12-30","related":[{"cvss_score":9.5,"headline":"TrueConf Server Code Injection","id":"CVE-2026-72530","kev_date_added":"2026-08-20","published":"2026-08-19"},{"cvss_score":9.3,"headline":"TrueConf Server Missing Authentication for Critical Function","id":"CVE-2026-72529","kev_date_added":"2026-08-20","published":"2026-08-19"},{"cvss_score":7.3,"headline":"Code injection in n/a","id":"CVE-2025-66834","kev_date_added":null,"published":"2025-12-30"},{"cvss_score":4.3,"headline":"TrueConf Server cross-site request forgery","id":"CVE-2017-20120","kev_date_added":null,"published":"2022-06-29"},{"cvss_score":3.5,"headline":"Cross-site scripting in n/a","id":"CVE-2025-66823","kev_date_added":null,"published":"2025-12-30"}],"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":"total"},"state":"PUBLISHED","updated":"2026-01-02","vendors":["n/a"]},"summary":"Attackers can inject scripts into the meeting location field to achieve full account takeover when victims view the conference info page.","url":"https://insights.sbomify.com/CVE-2025-66824/"}