Advanced Online Voting SystemApplication · Campcodes

CVE-2025-9694

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 determined in Campcodes Advanced Online Voting System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/login.php. Executing manipulation of the argument Username can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

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 · moderate confidence

SQL injection vulnerability in Campcodes Advanced Online Voting System 1.0's /admin/login.php allows remote attackers to manipulate the Username argument to inject malicious SQL queries, potentially enabling authentication bypass, data exfiltration, or complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in login.php, implement strict input validation on the Username field, and conduct thorough security testing to verify the remediation.

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
Advanced Online Voting 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 Campcodes Advanced Online Voting System is installed
    Locate the web application directory on the server and verify the presence of the application files, particularly the /admin/login.php file.
    Affected if The file /admin/login.php exists in the web root or application directory.
  2. Verify the installed version is 1.0
    Check version files, headers, or any version identifier within the application (such as a readme, changelog, or version constant in the source code).
    Affected if The installed version is exactly 1.0.
  3. Confirm the admin login page is accessible
    Access the URL path /admin/login.php through the web server to verify the login form is available.
    Affected if The login page loads and accepts input on the Username field.
  4. Inspect the login.php source code for dynamic SQL
    Examine the /admin/login.php file for SQL query construction that uses the Username parameter without parameterized queries or prepared statements.
    Affected if The code constructs SQL queries by directly concatenating or embedding the Username input into the query string.
  5. Check if the Username parameter is not validated
    Review the login.php file to determine whether input validation, sanitization, or escaping is applied to the Username field before using it in SQL queries.
    Affected if No input validation or secure coding practices are found for the Username parameter.

The environment is affected if Campcodes Advanced Online Voting System version 1.0 is installed, the /admin/login.php file exists, and the Username parameter is used in dynamically constructed SQL queries without parameterized statements or input validation.

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 or prepared statements in login.php, implement strict input validation on the Username field, and conduct thorough security testing to verify the remediation.

Fix this in Advanced Online Voting System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9694 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