{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27094 exists.","fix":"No fix has been published for CVE-2025-27094 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27094 is a medium-severity vulnerability in Enalean Tuleap, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27094 and fix it if it is affected.\n\nWhat it is: CVE-2025-27094 is a medium-severity vulnerability in Enalean Tuleap, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27094 exists.\n\nAffected product: Enalean Tuleap. 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-27094/ (Markdown: https://insights.sbomify.com/CVE-2025-27094/index.md)","id":"CVE-2025-27094","markdown":"https://insights.sbomify.com/CVE-2025-27094/index.md","name":"CVE-2025-27094","record":{"aliases":["GHSA-r85g-9wjx-pw7f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Tuleap project management","requires_auth":"low_privilege","summary":"A malicious user can clear field configurations causing data loss or crash the tracker, impacting data integrity and availability in Tuleap.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tuleap","vendor":"enalean"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-440","name":"Expected Behavior Violation"}],"description":"Tuleap is an open-source suite designed to improve software development management and collaboration. A malicious user with access to a tracker could force-reset certain field configurations, leading to potential information loss. The display time attribute for the date field, the size attribute for the multiselectbox field, the default value, number of rows, and columns attributes for the text field, and the default value, size, and max characters attributes for the string field configurations are lost when added as criteria in a saved report. Additionally, in Tuleap Community Edition versions 16.4.99.1739806825 to 16.4.99.1739877910, this issue could be exploited to prevent access to tracker data by triggering a crash. This vulnerability has been fixed in Tuleap Community Edition 16.4.99.1739877910 and Tuleap Enterprise Edition 16.3-9 and 16.4-4.","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":"Tuleap allows default values to be cleared from field configuration","id":"CVE-2025-27094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"enalean:tuleap","products":["enalean:tuleap"],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"JumpServer has a Kubernetes Token Leak Vulnerability","id":"CVE-2025-27095"},"packages":[],"prev":{"headline":"Sliver does not restricted traffic between Wireguard clients.","id":"CVE-2025-27093"},"products":["tuleap"],"published":"2025-03-03","related":[{"cvss_score":9.8,"headline":"Business logic in n/a","id":"CVE-2018-17298","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-7538","kev_date_added":null,"published":"2018-03-12"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2014-7178","kev_date_added":null,"published":"2014-11-28"},{"cvss_score":8.8,"headline":"SQL injection in Tuleap","id":"CVE-2021-43806","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":8.8,"headline":"SQL injection in the \"SVN core\" commits browser","id":"CVE-2021-41154","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"SQL injection in CVS revisions browser","id":"CVE-2021-41155","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"The update of the CI job targeted by a widget is vulnerable to blind SQL injections","id":"CVE-2021-41148","kev_date_added":null,"published":"2021-10-15"}],"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-03-03","vendors":["Enalean"]},"summary":"A malicious user can clear field configurations causing data loss or crash the tracker, impacting data integrity and availability in Tuleap.","url":"https://insights.sbomify.com/CVE-2025-27094/"}