CVE-2025-50369
BaseFortify
Publication date: 2025-06-27
Last updated on: 2025-07-01
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anujk305 | medical_card_generation_system | 1.0 |
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?
This vulnerability is a Cross-Site Request Forgery (CSRF) in the Manage Card functionality of the PHPGurukul Medical Card Generation System 1.0. It allows an authorized admin's browser to be tricked into sending a GET request that deletes medical card records without verifying the origin of the request, potentially enabling unauthorized deletion of records.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized deletion of medical card records by exploiting an admin's authenticated session. This could result in data loss, disruption of medical card management, and potential operational issues within the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring for unauthorized GET requests to the /mcgs/admin/manage-card.php endpoint that perform delete actions without proper origin verification. Commands like using network traffic analysis tools (e.g., tcpdump or Wireshark) to filter HTTP GET requests to this endpoint can help. For example, using tcpdump: tcpdump -i any -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep '/mcgs/admin/manage-card.php'. Additionally, reviewing web server logs for suspicious GET requests to this endpoint can help identify exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing CSRF protection on the /mcgs/admin/manage-card.php endpoint, such as requiring a CSRF token for state-changing requests, changing the delete operation from GET to POST method, and validating the origin or referer headers. Additionally, restricting access to authorized admins and monitoring for suspicious requests can help reduce risk until a patch is applied.