{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61599 exists.","fix":"No fix has been published for CVE-2025-61599 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61599 is a medium-severity cross-site scripting vulnerability in Emlog Emlog, published on 3 Oct 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-61599 and fix it if it is affected.\n\nWhat it is: CVE-2025-61599 is a medium-severity cross-site scripting vulnerability in Emlog Emlog, published on 3 Oct 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-61599 exists.\n\nAffected product: Emlog Emlog. 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-61599/ (Markdown: https://insights.sbomify.com/CVE-2025-61599/index.md)","id":"CVE-2025-61599","markdown":"https://insights.sbomify.com/CVE-2025-61599/index.md","name":"CVE-2025-61599","record":{"aliases":["GHSA-rm5c-mjpg-vm89"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Emlog CMS","requires_auth":"low_privilege","summary":"Authenticated users can inject malicious JavaScript via the Twitter feature, leading to script execution in other users' browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"emlog","vendor":"emlog"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Emlog is an open source website building system. A stored Cross-Site Scripting (XSS) vulnerability exists in the \"Twitter\"feature of EMLOG Pro 2.5.21 and below. An authenticated user with privileges to post a \"Twitter\" message can inject arbitrary JavaScript code. The malicious script is stored on the server and gets executed in the browser of any user, including administrators, when they click on the malicious post to view it. This issue does not currently have a fix.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Emlog is Vulnerable to Stored Cross-Site Scripting (XSS) in \"Twitter\" Feature via Markdown Input","id":"CVE-2025-61599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"emlog:emlog","products":["emlog:emlog"],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Unbounded Memory Allocation in Stalwart IMAP parser","id":"CVE-2025-61600"},"packages":[],"prev":{"headline":"Discourse is missing Cache-Control response header on error responses","id":"CVE-2025-61598"},"products":["emlog"],"published":"2025-10-03","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-29401","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-25783","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-44973","kev_date_added":null,"published":"2023-10-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-44974","kev_date_added":null,"published":"2023-10-03"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2023-43291","kev_date_added":null,"published":"2023-09-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-23379","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-40883","kev_date_added":null,"published":"2021-12-14"}],"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":"2025-10-03","vendors":["emlog"]},"summary":"Authenticated users can inject malicious JavaScript via the Twitter feature, leading to script execution in other users' browsers.","url":"https://insights.sbomify.com/CVE-2025-61599/"}