CVE-2025-50369
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Cross-Site Request Forgery (CSRF) vulnerability exists in the Manage Card functionality (/mcgs/admin/manage-card.php) of PHPGurukul Medical Card Generation System 1.0. The vulnerable endpoint allows an authorized admin to delete medical card records by sending a simple GET request without verifying the origin of the request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA CSRF vulnerability exists in PHPGurukul Medical Card Generation System 1.0 at /mcgs/admin/manage-card.php where the delete medical card function accepts GET requests without validating anti-CSRF tokens or verifying request origin, allowing attackers to trick authenticated administrators into unknowingly deleting card records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm PHPGurukul Medical Card Generation System 1.0 is installedLocate the file /mcgs/admin/manage-card.php in your web root directory. If the file exists, the product is installed.Affected if The file /mcgs/admin/manage-card.php exists on the server.
-
Verify delete action accepts GET requestsExamine the manage-card.php source code around the delete functionality. Look for delete operations that process $_GET parameters (e.g., $_GET['id'] or $_GET['delid']) without requiring a POST form submission.Affected if The delete medical card function processes requests via $_GET without requiring a POST method.
-
Check for anti-CSRF token implementationSearch the manage-card.php file for anti-CSRF token generation and validation functions. Look for tokens named类似 'csrf_token', 'token', or 'csrf' that are validated before delete operations execute.Affected if No anti-CSRF token is generated, stored, or validated when the delete function processes requests.
-
Inspect Referer/Origin header validationSearch the manage-card.php file for server-side checks of $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_ORIGIN'] headers that validate the request origin before allowing the delete action.Affected if The delete function does not validate the Referer or Origin header to verify request legitimacy.
You are affected if the manage-card.php file exists and its delete function accepts GET requests without anti-CSRF token or Referer/Origin validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens for state-changing operations and change the delete action from GET to POST method; additionally validate the Referer/Origin header to verify request legitimacy.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50369 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data