dbcve.org
Online Polling SystemApplication · Razormist

CVE-2025-9699

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-30
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 was detected in SourceCodester Online Polling System Code 1.0. This vulnerability affects unknown code of the file /admin/checklogin.php. The manipulation of the argument myusername results in sql injection. The attack may be performed from a remote location. The exploit is now 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 login authentication of SourceCodester Online Polling System 1.0. The 'myusername' parameter in /admin/checklogin.php is not properly sanitized before being used in a SQL query, allowing remote attackers to inject arbitrary SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in checklogin.php. Additionally, implement input validation and apply principle of least privilege to the database user account.

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
Online Polling 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 you are running the Online Polling System
    Identify the web application installed on your server. Check the application name, title, or footer of the web pages for 'Online Polling System', 'Razormist', or 'SourceCodester'.
    Affected if The application name does not match Online Polling System from SourceCodester or Razormist.
  2. Verify the installed version is 1.0
    Check for a version file, readme.txt, or any documentation within the application root directory. Alternatively, look for version strings in the source code comments or configuration files.
    Affected if The installed version is not exactly 1.0.
  3. Locate the vulnerable PHP file
    Navigate to your web server's document root and search for the file /admin/checklogin.php. Confirm its existence.
    Affected if The file /admin/checklogin.php does not exist.
  4. Inspect the vulnerable code pattern
    Open /admin/checklogin.php in a text editor. Search for SQL queries that incorporate the 'myusername' parameter without using prepared statements or parameter binding. Look for code that directly inserts $_POST['myusername'] into a SQL string.
    Affected if The code contains unsanitized use of 'myusername' in a SQL query, typically shown as a direct concatenation or string interpolation without mysqli_prepare or PDO prepare.

You are affected if you have Razormist/SourceCodester Online Polling System version 1.0 installed and the file /admin/checklogin.php contains direct SQL query construction using the myusername parameter without prepared statements.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in checklogin.php. Additionally, implement input validation and apply principle of least privilege to the database user account.

Recommended fix High confidence
  1. 1. Locate the vulnerable file /admin/checklogin.php
  2. 2. Identify the SQL query that uses the 'myusername' parameter without sanitization
  3. 3. Replace the vulnerable query with a parameterized query (prepared statement) using PDO or mysqli
  4. 4. For PDO: Use $pdo->prepare('SELECT * FROM admin WHERE username = ?') followed by $stmt->execute([$myusername])
  5. 5. For mysqli: Use $stmt = $conn->prepare('SELECT * FROM admin WHERE username = ?') followed by $stmt->bind_param('s', $myusername)
  6. 6. Remove any direct string concatenation in SQL queries
  7. 7. Apply the same fix to all other files that construct SQL queries with user input
  8. 8. Test the login functionality after implementing the fix
Caveat No official upgrade path available; manual code remediation required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Polling System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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