CVE-2025-48991
BaseFortify
Publication date: 2025-06-25
Last updated on: 2025-08-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| enalean | tuleap | to 16.7-5 (exc) |
| enalean | tuleap | to 16.8.99.1748845907 (exc) |
| enalean | tuleap | From 16.8 (inc) to 16.8-3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-48991 is a moderate severity vulnerability in the Tuleap software affecting versions prior to Community Edition 16.8.99.1748845907 and Enterprise Editions before 16.8-3 and 16.7-5. It is caused by missing Cross-Site Request Forgery (CSRF) protection in the administration interface for tracker canned responses. This allows an attacker to trick authenticated users into making unauthorized changes to canned responses without their consent by exploiting the lack of CSRF token verification in create, update, or delete operations. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to perform unauthorized modifications to the canned responses in the Tuleap tracker administration interface. Although it does not affect confidentiality, it has a low impact on integrity and availability, meaning an attacker could cause minor disruptions or unauthorized changes to canned responses, potentially affecting workflow or communication templates within the software development management process. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if your Tuleap installation is running a version prior to Community Edition 16.8.99.1748845907 or Enterprise Editions before 16.8-3 and 16.7-5, as these versions lack CSRF protection in the canned responses administration interface. On the system, you can verify the Tuleap version by running commands like `tuleap --version` or checking the installed package version. Additionally, monitoring HTTP POST requests to the canned responses administration URLs for missing CSRF tokens can help detect exploitation attempts. However, no specific network detection commands are provided in the resources. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, upgrade your Tuleap installation to Community Edition 16.8.99.1748845907 or Enterprise Editions 16.8-3 or 16.7-5, which include the patch adding CSRF protection to the canned responses administration interface. If upgrading is not immediately possible, restrict access to the administration interface to trusted users only, and educate users to avoid interacting with untrusted links or pages while authenticated. Applying the patch from commit cbf9b2a38e33dfd755dc2ccf074126b598a78274 will ensure CSRF tokens are required for all state-changing operations, preventing unauthorized modifications. [1, 2, 3]