CVE-2023-48434
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 · uneditedOnline Voting System Project v1.0 is vulnerable to multiple Unauthenticated SQL Injection vulnerabilities. The 'username' parameter of the reg_action.php resource does not validate the characters received and they are sent unfiltered to the database.
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 confidenceOnline Voting System v1.0 contains an unauthenticated SQL injection vulnerability in the username parameter of reg_action.php. The application fails to validate or sanitize user input before embedding it directly into SQL queries, allowing attackers to manipulate query logic and potentially extract, modify, or delete 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 applicationLocate and examine the application's source files or banner/version information to confirm it is Projectworlds Online Voting System version 1.0Affected if The application is Projectworlds Online Voting System version 1.0 and the source files are present
-
Locate reg_action.phpSearch the web root directory for the file reg_action.php - this is typically found in the admin or registration-related folder of the Online Voting SystemAffected if The file reg_action.php exists in the application directory
-
Verify vulnerable code pattern in reg_action.phpOpen reg_action.php and examine the PHP code around the username parameter handling. Look for SQL queries that directly concatenate or embed the username parameter without using prepared statements or parameterized queriesAffected if The code shows direct embedding of the username parameter into SQL queries (e.g., "SELECT * FROM users WHERE username='" . $_POST['username'] . "'") without input sanitization or prepared statements
-
Confirm unauthenticated access is possibleVerify that reg_action.php is accessible without authentication - check if the endpoint can be reached directly via HTTP/HTTPS without login credentialsAffected if The reg_action.php endpoint is reachable without any authentication requirement
-
Test username parameter for SQL injection behaviorIf authorized and within scope, send a crafted username value containing SQL meta-characters (e.g., username with a single quote ') to reg_action.php and observe the application's response for SQL syntax errors or unexpected behaviorAffected if The application returns database error messages or exhibits unexpected behavior when special SQL characters are submitted in the username parameter
You are affected if you are running Projectworlds Online Voting System version 1.0 and the reg_action.php file contains direct SQL query construction with the username parameter without prepared statements or input sanitization.
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/prepared statements in reg_action.php and all other affected files to ensure user input is treated as data rather than executable code.
- 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-2023-48434 — 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-2023-48434 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