CVE-2026-5534
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 was identified in itsourcecode Online Enrollment System 1.0. This affects an unknown function of the file /sms/user/index.php?view=edit&id=10 of the component Parameter Handler. Such manipulation of the argument USERID leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might 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 · moderate confidenceSQL injection vulnerability in itsourcecode Online Enrollment System 1.0 allows remote attackers to inject malicious SQL queries through the USERID parameter in the /sms/user/index.php file when editing user profiles. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries, potentially exposing or modifying sensitive enrollment data.
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.
-
Identify the installed application versionLocate the application's source files and check for version identifiers in files like README, about page, or version configuration files. Search for 'Online Enrollment System' and '1.0' references in the web root directory.Affected if The application is itsourcecode Online Enrollment System version 1.0 or if version cannot be determined but the application appears to be this specific system.
-
Verify the vulnerable file existsCheck if the file /sms/user/index.php exists in the web server's document root. This is the specific path mentioned in the CVE as containing the vulnerable parameter handler.Affected if The file /sms/user/index.php exists in the deployed application.
-
Confirm the vulnerable parameter is in useInspect the source code of /sms/user/index.php and look for the 'USERID' parameter handling in the context of the 'edit' view. Search for $_GET['USERID'] or $_REQUEST['USERID'] usage without sanitization.Affected if The code shows direct use of USERID parameter from user input (GET/REQUEST) without visible sanitization or parameterized queries.
-
Determine exposure to remote usersCheck if the application is accessible over the network. Verify the web server configuration exposes /sms/user/ endpoint to untrusted users. Test accessing the URL path /sms/user/index.php?view=edit externally.Affected if The application is accessible to untrusted network users without authentication protection on the user management interface.
A user is affected if they have itsourcecode Online Enrollment System 1.0 deployed with the /sms/user/index.php file accessible and the USERID parameter handler lacks proper 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 prepared statements/parameterized queries for all database operations involving user-supplied input, particularly the USERID parameter. Additionally, implement input validation and apply principle of least privilege to database accounts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5534 — 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-5534 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