CVE-2026-5801
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 · uneditedImproper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Semtek Informatics Software Consulting Trade Ltd. Co. SEM-PMP allows Command Line Execution through SQL Injection. This issue affects SEM-PMP: through 23042026.
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 confidenceA SQL injection vulnerability in SEM-PMP allows attackers to execute arbitrary SQL commands, which can be escalated to operating system command execution. The vulnerability affects all versions through 23042026 and is classified as critical due to the potential for complete system compromise.
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
- 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 SEM-PMP installation and versionLocate the SEM-PMP application directory or use package management commands (e.g., rpm -qa, dpkg -l, or vendor-specific tooling) to list the installed SEM-PMP version. Check configuration files or the application banner for version information.Affected if The installed version is 23042026 or any earlier version.
-
Confirm database connectivity is activeExamine SEM-PMP configuration files for database connection strings, JDBC/ODBC settings, or database user credentials. Verify the application is configured to connect to any SQL database (MySQL, PostgreSQL, MSSQL, Oracle, etc.).Affected if SEM-PMP is configured with an active database connection, as SQL injection requires a database interface to be exploitable.
-
Identify SQL interaction endpointsReview SEM-PMP web service definitions, API routes, or input parameters that accept user-supplied data and pass it to SQL queries. Check for direct string concatenation in database query code.Affected if The application contains endpoints or code paths that process user input into SQL queries without visible use of parameterized queries or prepared statements.
-
Check for privilege escalation pathwaysInspect the database user privileges assigned to SEM-PMP (e.g., via GRANT statements or application DB config). Look for DB user permissions that allow xp_cmdshell, sys_exec, INTO OUTFILE, or similar OS-level commands.Affected if The database user has privileges beyond basic CRUD operations, enabling potential OS command execution escalation from SQL injection.
You are affected if SEM-PMP version is 23042026 or lower and the application has an active database connection with input fields that could accept SQL injection payloads.
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 dataUpgrade to a version beyond 23042026 once available, and implement parameterized queries/prepared statements for all database interactions. Restrict database user privileges to prevent command execution escalation.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5801 — 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-5801 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