dbcve.org
Medical Card Generation SystemApplication · Anujk305

CVE-2024-10297

HIGH · 7.2 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A vulnerability was found in PHPGurukul Medical Card Generation System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/changeimage.php of the component Managecard Edit Image Page. The manipulation of the argument editid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 confidence

SQL injection vulnerability in PHPGurukul Medical Card Generation System 1.0 allows remote attackers to inject arbitrary SQL commands via the editid parameter in /admin/changeimage.php. The Managecard Edit Image Page component fails to properly sanitize user input before using it in SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements to sanitize the editid parameter. If no vendor patch exists, implement input validation and consider temporary WAF protection until proper code fixes are applied.

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
Medical Card Generation SystemApplication
Affected:= 1.0

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the application installation
    Locate PHPGurukul Medical Card Generation System files on the server. Check web root directories for the application structure, particularly looking for folders containing 'medical' or 'card' in the name, or the typical PHPGurukul layout.
    Affected if The application is installed and accessible on the web server.
  2. Verify the installed version
    Check version.php, README.txt, or any version file within the application root for the version number. Compare it to the affected version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Identify the vulnerable file
    Locate the file /admin/changeimage.php within the web application directory structure. This is the file containing the vulnerable code.
    Affected if The file /admin/changeimage.php exists in the installation.
  4. Confirm admin interface accessibility
    Check if the /admin/ directory is accessible via HTTP/HTTPS. Attempt to access the admin login page or verify authentication status.
    Affected if The admin panel is accessible without requiring authentication or with valid admin credentials.
  5. Inspect the vulnerable code pattern
    Review the source code of changeimage.php and search for SQL query patterns that use the 'editid' parameter directly in queries without using prepared statements, parameter binding, or input sanitization functions.
    Affected if The code shows editid being directly concatenated into SQL queries without sanitization.

A user is affected if they are running PHPGurukul Medical Card Generation System version 1.0 with the /admin/changeimage.php file accessible and the editid parameter being used in unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements to sanitize the editid parameter. If no vendor patch exists, implement input validation and consider temporary WAF protection until proper code fixes are applied.

Fix this in Medical Card Generation System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10297 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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