CVE-2026-4836
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 detected in code-projects Accounting System 1.0. The affected element is an unknown function of the file /my_account/delete.php. Performing a manipulation of the argument cos_id results in sql injection. It is possible to initiate the attack remotely. The exploit is now 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 confidenceSQL injection vulnerability in code-projects Accounting System 1.0 allows remote attackers to inject malicious SQL queries via the cos_id parameter in /my_account/delete.php. The lack of input sanitization or parameterized queries in the delete operation permits attackers to manipulate database queries.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Accounting System installationLocate the web application root directory and confirm the presence of the code-projects Accounting System. Look for characteristic files such as index.php, login pages, or the /my_account/ directory structure.Affected if The code-projects Accounting System 1.0 is installed on the server.
-
Confirm vulnerable file existsInspect the /my_account/ directory within the web root for the presence of delete.php. This file handles the delete operation for the cos_id parameter.Affected if The file /my_account/delete.php exists in the application.
-
Check application versionReview version.php, README files, or the database for a version identifier. Compare against the affected version 1.0.Affected if The installed version is code-projects Accounting System 1.0.
-
Verify parameter acceptanceTest the delete.php endpoint with the cos_id parameter by sending a request with a single quote value (e.g., cos_id=1') and observe if SQL errors are returned or if the input is processed without sanitization.Affected if The cos_id parameter accepts unvalidated input and the application reflects SQL syntax errors or processes the injection without sanitization.
-
Inspect delete.php for SQL constructionOpen delete.php and examine how the cos_id parameter is incorporated into SQL queries. Look for direct string concatenation or lack of prepared statements/parameter binding.Affected if The code uses direct string concatenation with the cos_id parameter in SQL queries rather than parameterized queries or prepared statements.
A user is affected if they have code-projects Accounting System version 1.0 installed with the vulnerable /my_account/delete.php file that accepts unsanitized cos_id input in SQL queries.
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 in delete.php, apply strict input validation on the cos_id parameter, and enforce least privilege database access. Consider deploying a WAF as an additional layer of defense.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4836 — 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-4836 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