dbcve.org
Intern Membership Management SystemApplication · Carmelo

CVE-2025-8494

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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, which was classified as critical, has been found in code-projects Intern Membership Management System 1.0. This issue affects some unknown processing of the file /admin/delete_student.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated 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 the Intern Membership Management System 1.0's /admin/delete_student.php file. The ID parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.

MitigationImplement parameterized queries or prepared statements for all database operations, especially where user input (the ID parameter) is used. Apply input validation and principle of least privilege to the database user.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Intern Membership Management System installation
    Locate the web application directory. Check for files or directories named 'Intern Membership Management System', 'carmelo', or similar. Look for the presence of delete_student.php in the /admin/ subdirectory.
    Affected if The application directory contains delete_student.php in an /admin/ folder and the software is identified as Carmelo Intern Membership Management System version 1.0
  2. Verify the vulnerable delete_student.php file exists
    Inspect the application's file structure for /admin/delete_student.php. This is the file where the unsanitized ID parameter is used in SQL queries.
    Affected if The file /admin/delete_student.php exists in the web application root directory
  3. Confirm admin panel accessibility
    Check if the /admin/ directory is web-accessible without proper authentication or if authentication can be bypassed. Attempt to access delete_student.php directly.
    Affected if The delete_student.php endpoint is accessible without requiring valid admin authentication or session
  4. Identify database configuration and input handling
    Review the delete_student.php source code. Look for SQL query construction using the ID parameter (e.g., $_GET['id'] or $_POST['id']) without parameterized queries, prepared statements, or proper sanitization functions like mysqli_real_escape_string or PDO prepared statements.
    Affected if The ID parameter is directly concatenated into SQL queries without using prepared statements or input sanitization functions
  5. Check web server logs for suspicious SQL injection attempts
    Review web server access and error logs for unusual patterns in requests to /admin/delete_student.php, such as SQL metacharacters (' - ; DROP, etc.) in the ID parameter.

A user is affected if they have Carmelo Intern Membership Management System 1.0 installed with the /admin/delete_student.php file accessible and the ID parameter is used in SQL queries without prepared statements or input sanitization.

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

Implement parameterized queries or prepared statements for all database operations, especially where user input (the ID parameter) is used. Apply input validation and principle of least privilege to the database user.

Fix this in Intern Membership Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8494 — 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-2025-8494 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