CVE-2025-7950
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 Public Chat Room 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /login.php. The manipulation of the argument Username 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 confidenceSQL injection vulnerability in the /login.php file of Public Chat Room 1.0 allows remote attackers to inject malicious SQL queries through the Username parameter. The critical CVSS score of 9.8 indicates potential for complete compromise including authentication bypass, data exfiltration, or database takeover.
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 if Public Chat Room is installedSearch the web server document root for files named 'login.php' or directories containing 'chat' in the path. Check for the presence of the application files.Affected if The Fabian Public Chat Room application files are present on the server.
-
Confirm the installed version is 1.0Look for a version file, check the header comments in login.php, or search for version strings within the application source code.Affected if The installed version is Fabian Public Chat Room 1.0.
-
Locate the vulnerable login.php fileFind the /login.php file in the application directory. Inspect the file to confirm it handles user authentication.Affected if The login.php file exists and handles the Username parameter for authentication.
-
Verify the Username parameter is processed dynamicallyOpen login.php and examine how the Username parameter is used in SQL queries. Look for string concatenation or direct interpolation of user input into SQL statements without using prepared statements or parameter binding.Affected if The Username input is directly concatenated into SQL queries without parameterized queries or prepared statements.
-
Check if the application database is accessibleVerify the database configuration file exists (such as config.php or db.php) and contains database connection credentials. Confirm the application connects to a MySQL or SQLite database.Affected if The application has an active database connection and the login.php file processes SQL queries against it.
A user is affected if Fabian Public Chat Room version 1.0 is installed and the login.php file processes the Username parameter using dynamic SQL concatenation rather than parameterized queries.
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 parameterized queries or prepared statements in login.php and all other files handling user input. Apply input validation and enable database-level protections such as least-privilege database accounts.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7950 — 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-7950 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