dbcve.org
InjectionWeakness · CWE-74

CVE-2026-5150

HIGH · 7.3 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 security vulnerability has been detected in code-projects Accounting System 1.0. This issue affects some unknown processing of the file /viewin_costumer.php of the component Parameter Handler. Such manipulation of the argument cos_id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed publicly 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 the code-projects Accounting System 1.0 allows remote attackers to manipulate the cos_id parameter in /viewin_costumer.php to inject malicious SQL queries. The lack of proper input sanitization in the Parameter Handler component enables attackers to potentially access, modify, or delete database contents.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation for the cos_id parameter. Apply principle of least privilege to database accounts.

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 checks

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

  1. Verify the application is code-projects Accounting System 1.0
    Locate the application installation directory and check for version identification files (such as version.php, README, or installer files) or check the web server banner for the application name and version.
    Affected if The installed application is code-projects Accounting System version 1.0 or earlier without a version identifier file indicating otherwise.
  2. Confirm the vulnerable file exists
    Search for the file /viewin_costumer.php in the web root directory. On Linux, use: find /var/www -name 'viewin_costumer.php' or locate the application's document root and check for this specific file.
    Affected if The file viewin_costumer.php exists in the web-accessible directory.
  3. Inspect the SQL query handling for cos_id
    Open viewin_costumer.php and examine how the cos_id parameter is used in database queries. Look for direct inclusion of $_GET['cos_id'] or $_POST['cos_id'] in SQL statements without using prepared statements or parameter binding.
    Affected if The code contains SQL queries that concatenate or embed the cos_id parameter directly without sanitization or parameterization.
  4. Check for prepared statements or input validation
    Review the code around the cos_id parameter handling. Search for function calls like mysqli_prepare, PDO::prepare, or any input validation/sanitization functions applied to cos_id before database operations.
    Affected if No prepared statements, parameterized queries, or input validation functions are found for the cos_id parameter in the SQL execution context.
  5. Test the parameter with a safe probe (optional)
    If authorized and in a non-production environment, send a request such as: GET /viewin_costumer.php?cos_id=1' OR '1'='1 and observe whether the application returns database errors or unexpected results indicating SQL injection is possible.
    Affected if The application returns SQL syntax errors in the response or behaves unexpectedly with the test payload, indicating the parameter is vulnerable to injection.

The environment is affected if code-projects Accounting System 1.0 is running and the file viewin_costumer.php exists with unprotected dynamic SQL queries using the cos_id parameter.

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

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation for the cos_id parameter. Apply principle of least privilege to database accounts.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5150 — 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-5150 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