CVE-2025-5225
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, which was classified as critical, was found in Campcodes Advanced Online Voting System 1.0. This affects an unknown part of the file /index.php. The manipulation of the argument voter 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 confidenceA critical SQL injection vulnerability exists in Campcodes Advanced Online Voting System 1.0 in the /index.php file. The 'voter' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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 the application files and check version documentation, headers, or meta files. Look for version indicators in the source code, README files, or admin panels.Affected if The installed version is Campcodes Advanced Online Voting System 1.0
-
Verify the vulnerable endpoint existsCheck if the /index.php file exists in the web root of the application.Affected if The file /index.php is present and accessible via the web server
-
Confirm the voter parameter is acceptedSubmit a request to /index.php with a voter parameter (e.g., ?voter=test) and verify the application processes it without rejecting or sanitizing the input.Affected if The voter parameter is accepted and reflected in the response without validation or error messages
-
Test for SQL injection in the voter parameterSend a SQL injection test payload via the voter parameter (e.g., voter=1' OR '1'='1) and observe if the application returns database errors, unexpected results, or behaves differently than with normal input.Affected if The application returns SQL syntax errors, database information, or allows manipulation of query logic through the voter parameter
-
Review source code for lack of prepared statementsExamine the PHP code in /index.php and related database files to check if queries use prepared statements or parameterized queries, or if user input is concatenated directly into SQL strings.Affected if Code shows direct string concatenation of the voter parameter into SQL queries without using prepared statements or input sanitization
A user is affected if they are running Campcodes Advanced Online Voting System version 1.0 and the /index.php endpoint accepts the voter parameter without proper input validation or 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 prepared statements/parameterized queries in index.php and any other files handling the voter parameter to neutralize SQL injection vectors.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5225 — 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-5225 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