CVE-2025-8339
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 vulnerability was found in code-projects Intern Membership Management System 1.0. It has been classified as critical. This affects an unknown part of the file /student_login.php. The manipulation of the argument user_name/password leads to sql injection. It is possible to initiate the attack 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 confidenceSQL injection vulnerability in the Intern Membership Management System 1.0 allows remote attackers to inject malicious SQL queries via the user_name and password parameters in /student_login.php. The lack of proper input sanitization or parameterized queries enables attackers to bypass authentication or exfiltrate database contents.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed application versionLocate and inspect any version files, README files, or admin panels within the web application directory that indicate the software version. Check the source code for version comments or the main entry point for version information.Affected if The installed version is Carmelo Intern Membership Management System 1.0
-
Verify the presence of student_login.phpSearch the web root directory for the file student_login.php. This file is typically located in the application's main web directory.Affected if The file student_login.php exists in the web application directory
-
Examine the login processing codeOpen student_login.php and review the code handling the user_name and password parameters. Look for SQL query construction that directly incorporates these parameters without using prepared statements or parameter binding.Affected if The code constructs SQL queries using user-supplied input from user_name or password without parameterized queries or input sanitization
-
Confirm database interaction methodReview how the application connects to the database and executes queries. Check if database functions used (such as mysqli_query, mysql_query, PDO query, or similar) are called with string concatenation or interpolation of user inputs.Affected if User inputs are concatenated directly into SQL query strings before execution
-
Test the login endpoint for injection responseIf the application is accessible, observe the response when submitting special SQL characters (such as single quotes) in the user_name or password fields. Compare the response behavior to normal login attempts.Affected if The application returns database error messages or exhibits unexpected behavior when SQL special characters are submitted
A defender is affected if they are running Carmelo Intern Membership Management System version 1.0 and the student_login.php file contains SQL queries built with direct string concatenation of user_name and password parameters.
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 dataReplace dynamic SQL queries with prepared statements/parameterized queries in student_login.php, implement input validation, and apply principle of least privilege to database accounts. Conduct full codebase audit for additional SQL injection points.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8339 — 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-8339 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