CVE-2025-6476
BaseFortify
Publication date: 2025-06-22
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | gym_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
| 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-6476 is a Cross-Site Request Forgery (CSRF) vulnerability in SourceCodester Gym Management System version 1.0. The system does not verify the origin of sensitive requests and lacks CSRF token validation. This allows attackers to create malicious web pages that can submit unauthorized requests on behalf of authenticated users without their consent, potentially triggering unintended actions such as adding or modifying student records. The vulnerability affects the integrity of the system's business logic and can be exploited remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to perform unauthorized actions on the affected system by tricking authenticated users into visiting malicious web pages. Such actions may include adding or modifying student records or other sensitive operations, potentially compromising the system's business logic. If exploited in sensitive contexts like payments or privilege escalations, the impact could be severe. The exploit is easy to perform and publicly available, increasing the risk of exploitation. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing whether the system processes unauthorized POST requests without verifying CSRF tokens or the origin of the request. One approach is to craft a test HTML form that submits POST data to the vulnerable endpoint (/admin/student_action.php) with parameters such as student_name, student_roll_number, student_dob, student_course_id, student_emailid, student_password, student_id, and action=Add, and observe if the server processes the request without validation. Network monitoring tools can be used to detect suspicious POST requests to this endpoint. Specific commands are not provided in the resources, but manual testing with crafted HTML forms and monitoring HTTP requests to the vulnerable endpoint is recommended. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing dynamically generated CSRF tokens for all sensitive operations and validating them server-side, verifying the Referer or Origin headers to ensure requests come from trusted sources, setting cookies with the SameSite attribute (e.g., SameSite=Strict) and Secure flag to prevent cross-site exploitation, and restricting sensitive operations by adding additional verification steps such as multi-factor authentication or explicit user confirmation. If possible, replacing the affected product with an alternative solution is also suggested. [2, 3]