{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25460 exists.","fix":"No fix has been published for CVE-2025-25460 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25460 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-25460 and fix it if it is affected.\n\nWhat it is: CVE-2025-25460 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2025. An attacker needs administrator access to exploit it, 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-25460 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-25460/ (Markdown: https://insights.sbomify.com/CVE-2025-25460/index.md)","id":"CVE-2025-25460","markdown":"https://insights.sbomify.com/CVE-2025-25460/index.md","name":"CVE-2025-25460","record":{"aliases":["GHSA-rfwv-x796-g3w9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FlatPress blog software","requires_auth":"high_privilege","summary":"Authenticated attackers can inject malicious JavaScript into blog posts via the Add Entry feature, leading to script execution for other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flatpress","vendor":"flatpress"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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":"A stored Cross-Site Scripting (XSS) vulnerability was identified in FlatPress 1.3.1 within the \"Add Entry\" feature. This vulnerability allows authenticated attackers to inject malicious JavaScript payloads into blog posts, which are executed when other users view the posts. The issue arises due to improper input sanitization of the \"TextArea\" field in the blog entry submission form.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-02-22","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-02-22T03:48:56Z","kind":"github_poc","ref":"https://github.com/RoNiXxCybSeC0101/CVE-2025-25460","stars":1,"title":"Cross Site Scripting Vulnerability in Flatpress CMS "}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-25460","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-25461"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-25458"},"products":["n/a"],"published":"2025-02-24","related":[{"cvss_score":8.8,"headline":"PHP Remote File Inclusion in flatpressblog/flatpress","id":"CVE-2022-4606","kev_date_added":null,"published":"2022-12-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-22761","kev_date_added":null,"published":"2021-07-29"},{"cvss_score":8.1,"headline":"Stored XSS in flatpressblog/flatpress","id":"CVE-2024-4023","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2024-41290","kev_date_added":null,"published":"2024-10-02"},{"cvss_score":8.1,"headline":"Cross-site Scripting (XSS) - Stored in flatpressblog/flatpress","id":"CVE-2023-1104","kev_date_added":null,"published":"2023-03-01"},{"cvss_score":8.1,"headline":"Path Traversal in flatpressblog/flatpress","id":"CVE-2023-0947","kev_date_added":null,"published":"2023-02-22"},{"cvss_score":8,"headline":"Cross-Site Request Forgery (CSRF) in flatpressblog/flatpress","id":"CVE-2024-9847","kev_date_added":null,"published":"2025-03-20"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-24","vendors":["n/a"]},"summary":"Authenticated attackers can inject malicious JavaScript into blog posts via the Add Entry feature, leading to script execution for other users.","url":"https://insights.sbomify.com/CVE-2025-25460/"}