dbcve.org
Document Management SystemApplication · Admerc

CVE-2026-3133

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in itsourcecode Document Management System 1.0. This issue affects some unknown processing of the file /loging.php of the component Login. The manipulation of the argument Username leads to sql injection. Remote exploitation of the attack is possible. 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 · moderate confidence

SQL injection vulnerability in itsourcecode Document Management System 1.0 login component (/loging.php). The Username parameter is vulnerable to SQL injection, allowing remote attackers to inject malicious SQL queries. The CVSS 9.8 indicates critical severity with no authentication required for exploitation.

MitigationImplement parameterized queries/prepared statements for all database operations in the login functionality. Apply vendor patch when available. Consider deploying a WAF as a temporary compensating control.

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
Document Management SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Document Management System installation
    Check if the Document Management System web application is installed on the server by locating typical web root paths (e.g., /var/www/html, C:\inetpub\wwwroot) and searching for files containing 'document', 'dms', or 'login' in filenames. Look for the presence of /loging.php specifically.
    Affected if The Document Management System is found and the /loging.php file exists in the web directory.
  2. Verify the exact version installed
    Check version information in typical locations: the application's main index page header/footer, a /about.php or /version.php file, configuration files (config.php, settings.php), or the application's admin panel 'System Info' section. Compare the discovered version number to the affected range: version 1.0.
    Affected if The installed version is Document Management System version 1.0.
  3. Confirm /loging.php is accessible
    Attempt to access the login page via HTTP/HTTPS request to the suspected web root path with /loging.php appended. For example: http://[target]/loging.php. Verify the page loads and contains a login form with a Username input field.
    Affected if The /loging.php page loads and contains a login form with a Username parameter.
  4. Inspect login source code for direct SQL query handling
    If source code access is available, examine the /loging.php file and any included database connection files. Look for SQL queries that concatenate or embed the Username parameter directly into WHERE clauses without using parameterized queries or prepared statements.
    Affected if The login code constructs SQL queries using the Username parameter without parameterized binding.
  5. Check database logs for suspicious login attempts
    Review database query logs (MySQL general_log, PostgreSQL logs, or similar) for unusual SQL syntax in authentication queries, especially near timestamp patterns corresponding to login page access. Look for SQL metacharacters (' OR, UNION SELECT, etc.) in Username-related queries.
    Affected if Database logs show SQL injection payloads in queries originating from the login Username parameter.

The environment is affected if Document Management System version 1.0 is deployed and the /loging.php login page with a Username parameter is accessible without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries/prepared statements for all database operations in the login functionality. Apply vendor patch when available. Consider deploying a WAF as a temporary compensating control.

Fix this in Document Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3133 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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