CVE-2026-13535
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 flaw has been found in CodeAstro Human Resource Management System 1.0. This vulnerability affects the function GetFileInfo of the file hrsystem/application/models/Employee_model.php of the component View Endpoint. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been published 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 CodeAstro HR Management System 1.0's Employee_model.php GetFileInfo function. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the View endpoint.
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.
-
Confirm CodeAstro HR Management System installationLocate the application installation directory and verify the presence of CodeAstro HR Management System files. Check for version identifier files or headers that indicate version 1.0.Affected if The application is CodeAstro HR Management System version 1.0
-
Locate Employee_model.php and identify GetFileInfo functionSearch for the file Employee_model.php within the application source code. Open the file and locate the GetFileInfo function definition.Affected if Employee_model.php exists and contains a GetFileInfo function that handles the ID parameter
-
Inspect ID parameter handling in GetFileInfoWithin GetFileInfo, examine how the ID parameter is used in SQL queries. Look for direct string concatenation or interpolation of the ID parameter into SQL statements without proper sanitization.Affected if The ID parameter is directly concatenated into SQL queries without parameterized queries, prepared statements, or input validation
-
Verify View endpoint is accessibleIdentify if a View endpoint exists that calls the GetFileInfo function and accepts an ID parameter via GET or POST request. Check routing configuration or URL patterns.Affected if A View endpoint exists that passes user-supplied ID values to the vulnerable GetFileInfo function
-
Check for absence of prepared statementsReview the GetFileInfo function code for use of PDO prepared statements, mysqli prepared statements, or other parameterized query mechanisms. Confirm no $stmt->prepare() or similar calls are present.Affected if No prepared statements or parameter binding are used when constructing SQL queries with the ID parameter
The environment is affected if CodeAstro HR Management System 1.0 is installed, Employee_model.php contains a GetFileInfo function that directly uses the ID parameter in SQL queries without prepared statements, and the View endpoint is accessible to pass malicious ID values.
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 dataImplement parameterized queries/prepared statements to sanitize the ID parameter before using it in SQL queries. Alternatively, implement proper input validation and escaping. Apply the fix immediately as an exploit is publicly available.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13535 — 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-13535 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