CVE-2026-3153
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 has been found in itsourcecode Document Management System 1.0. Impacted is an unknown function of the file /register.php. Such manipulation of the argument Username leads to sql injection. It is possible to launch 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 confidenceSQL injection vulnerability in itsourcecode Document Management System 1.0 allows remote attackers to inject malicious SQL queries via the Username parameter in /register.php. The critical CVSS 9.8 score indicates complete compromise potential including data exfiltration or database takeover.
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 Document Management System installationSearch web server directories for files matching 'register.php' or directories containing 'document management' or 'dms' naming. Check web server access logs for requests to /register.php.Affected if The itsourcecode/Admerc Document Management System version 1.0 is installed and accessible via web.
-
Confirm installed versionCheck application version file, footer in web interface, or any version.txt/readme file in the web root. Compare against the affected version: 1.0.Affected if The installed version is Document Management System 1.0.
-
Verify register.php is accessibleAttempt to access the /register.php endpoint on the web server (e.g., GET request to yourserver/register.php). Check for HTTP 200 response.Affected if register.php is publicly accessible and returns a registration form.
-
Check for database interaction in register.phpInspect the source code of register.php for SQL query execution functions (mysqli_query, mysql_query, PDO::query, etc.) handling the Username parameter without parameterized statements.Affected if The Username parameter is used in dynamic SQL queries without prepared statements or proper sanitization.
-
Test for SQL injection vulnerabilitySubmit a SQL injection test payload in the Username field (e.g., ' OR '1'='1) and observe database errors or unexpected behavior in the response. This is an active test - ensure you have authorization.Affected if The application returns SQL error messages or behaves differently than expected, indicating unsanitized input is passed to the database.
A defender is affected if they are running itsourcecode/Admerc Document Management System version 1.0 with register.php accessible and the Username parameter handled in dynamic SQL 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 dataReplace dynamic SQL queries with parameterized statements/prepared statements in register.php to properly sanitize the Username input. If vendor patches are available, upgrade to the fixed version.
- Consultation2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3153 — 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-3153 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