CVE-2025-10076
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 weakness has been identified in SourceCodester Online Polling System 1.0. This affects an unknown function of the file /manage-profile.php. This manipulation of the argument email causes sql injection. The attack may be initiated remotely. The exploit has been made available to the public and could be exploited.
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 confidenceSQL injection vulnerability in SourceCodester Online Polling System 1.0 allows remote attackers to execute arbitrary SQL commands via the email parameter in /manage-profile.php. The vulnerability is exploitable without authentication and a public exploit exists.
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 any version file, header, or check the source code for version identifiers. In the web root, look for readme.txt, version.php, or check the page footer for version numbers.Affected if The installed version is Online Polling System 1.0 (also labeled as Razormist Online Polling System 1.0)
-
Verify manage-profile.php existsCheck if the file /manage-profile.php exists in the web root directory of the application.Affected if The file manage-profile.php is present in the deployed application
-
Inspect the email parameter handling in manage-profile.phpOpen manage-profile.php and search for the code handling the email parameter. Look for SQL queries that directly incorporate the email input without using prepared statements or parameter binding.Affected if The code constructs SQL queries using the email parameter directly (e.g., using concatenation or string interpolation) without parameterized queries or prepared statements
-
Confirm the endpoint is accessible without authenticationAttempt to access manage-profile.php directly via HTTP request without providing any authentication credentials.Affected if The page loads or responds to requests without requiring login or session authentication
-
Check for signs of active exploitationReview web server access logs for unusual or malicious SQL syntax in requests to manage-profile.php, particularly targeting the email parameter.Affected if Malicious SQL injection payloads appear in access logs for the email parameter
A system is affected if it runs Online Polling System version 1.0 and the manage-profile.php file contains vulnerable SQL query construction using the email parameter without prepared statements.
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 dataApply parameterized queries or prepared statements for the email parameter in manage-profile.php, or implement proper input validation and sanitization. Given the critical CVSS score (9.8) and public exploit availability, the affected endpoint should be secured or the system taken offline until a fix is deployed.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10076 — 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-10076 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