{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57768 exists.","fix":"No fix has been published for CVE-2025-57768 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57768 is a medium-severity cross-site scripting vulnerability in Alanaktion phproject, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-57768 and fix it if it is affected.\n\nWhat it is: CVE-2025-57768 is a medium-severity cross-site scripting vulnerability in Alanaktion phproject, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57768 exists.\n\nAffected product: Alanaktion phproject. 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-57768/ (Markdown: https://insights.sbomify.com/CVE-2025-57768/index.md)","id":"CVE-2025-57768","markdown":"https://insights.sbomify.com/CVE-2025-57768/index.md","name":"CVE-2025-57768","record":{"aliases":["GHSA-mhhg-qx37-g369"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Project management system","requires_auth":"none","summary":"Attackers can inject malicious scripts via the Planned Hours field in Phproject, leading to stored XSS and potential session hijacking.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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":"Phproject is a high performance full-featured project management system. From 1.8.0 to before 1.8.3, a Stored Cross-Site Scripting (XSS) vulnerability exists in the Planned Hours field when creating a new project. When sending a POST request to /issues/new/, the value provided in the Planned Hours field is included in the server response without any HTML encoding or sanitization. Because of this, an attacker can craft a malicious payload such as \u003cscript\u003ealert(1)\u003c/script\u003e and include it in the planned_hours parameter. The server reflects the input directly in the HTML of the project creation page, causing the browser to interpret and execute it. This vulnerability is fixed in 1.8.3.","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":"Stored XSS in “hours” fields when creating or editing an issue, using SQLite database","id":"CVE-2025-57768","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"FressRSS: Clickjacking can lead to XSS and/or privilege escalation","id":"CVE-2025-57769"},"packages":[],"prev":{"headline":"Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request","id":"CVE-2025-57767"},"products":["phproject"],"published":"2025-08-21","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-21","vendors":["Alanaktion"]},"summary":"Attackers can inject malicious scripts via the Planned Hours field in Phproject, leading to stored XSS and potential session hijacking.","url":"https://insights.sbomify.com/CVE-2025-57768/"}