CVE-2026-4235
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 itsourcecode Online Enrollment System 1.0. This issue affects some unknown processing of the file /sms/login.php. This manipulation of the argument user_email causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.
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 confidenceSQL injection vulnerability in itsourcecode Online Enrollment System 1.0's login.php file. The user_email parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. The public availability of the exploit increases risk of automated attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Locate the itsourcecode Online Enrollment System installationSearch the server for the 'login.php' file commonly found in the web root directory under the enrollment system folder. Common paths include /var/www/html/enrollment/, /www/enrollment/, or search for 'login.php' containing 'user_email' form field.Affected if The application is found and the login.php file exists in a web-accessible directory
-
Confirm the application version is 1.0Check for a version file, readme, or footer in the application that displays the version number. Alternatively, compare the login.php file against the known vulnerable version 1.0.Affected if The installed version is 1.0 or cannot be determined (assume affected)
-
Inspect login.php for unsanitized user_email parameter usageOpen login.php and search for the user_email parameter. Look for direct inclusion in SQL queries without prepared statements, parameterized queries, or escaping functions (like mysqli_real_escape_string, addslashes).Affected if The user_email parameter is directly concatenated into SQL queries without sanitization or prepared statements
-
Determine if the database module is in useCheck if the application connects to a MySQL/MariaDB database and uses the user_email field in authentication queries. Verify the login.php performs database lookups.Affected if The login.php performs database authentication using the user_email parameter
-
Verify the login.php is publicly accessibleConfirm the web server configuration allows HTTP/HTTPS access to the login.php endpoint. Check if the system is exposed to the internet or internal networks.Affected if The login.php is accessible from the network where potential attackers could reach it
A user is affected if the itsourcecode Online Enrollment System 1.0 is installed with its login.php accessible and the user_email parameter is used directly in SQL queries without prepared statements or 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 dataImplement prepared statements/parameterized queries for all database operations in login.php, particularly for the user_email parameter. Apply input validation and escaping as defense-in-depth. Deploy a WAF rule to block SQL injection attempts until the patch is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4235 — 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-2026-4235 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