CVE-2026-13525
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 CodeAstro Human Resource Management System 1.0. This issue affects the function emselectByCode of the file application/models/Employee_model.php of the component Update_Earn_Leave Endpoint. The manipulation of the argument emid results in sql injection. The attack can be launched 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 · high confidenceSQL injection vulnerability in CodeAstro HRMS 1.0 allows remote attackers to inject malicious SQL queries via the emid parameter in the emselectByCode function of Employee_model.php. The Update_Earn_Leave Endpoint does not properly sanitize user input before using it in 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 CodeAstro HRMS installationLocate the application by searching for files named 'Employee_model.php' or directories containing 'CodeAstro' or 'HRMS' in the web server document root.Affected if CodeAstro HRMS 1.0 is installed on the server.
-
Confirm application versionCheck for a version file, about page, or footer in the application that displays the version number. Compare against the known affected version 1.0.Affected if The installed version is CodeAstro HRMS 1.0.
-
Locate the vulnerable fileFind Employee_model.php in the application directory structure, typically under application/models/ or similar MVC folder.Affected if Employee_model.php exists in the application.
-
Inspect the emselectByCode functionOpen Employee_model.php and locate the emselectByCode function. Examine how the emid parameter is used in database queries - check if it is directly concatenated into SQL without escaping or parameterization.Affected if The emid parameter is used directly in SQL queries without prepared statements or input sanitization.
-
Verify Update_Earn_Leave endpoint accessibilityCheck if the Update_Earn_Leave endpoint exists and is accessible via HTTP. This is typically in the controllers folder, likely an Employee or Leave controller.Affected if The Update_Earn_Leave endpoint exists and can receive user input via the emid parameter.
The environment is affected if CodeAstro HRMS 1.0 is installed with the Employee_model.php file containing an unsanitized emid parameter in the emselectByCode function that the Update_Earn_Leave endpoint calls.
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 parameterized queries (prepared statements) in the emselectByCode function. Additionally, implement input validation for the emid parameter and apply least-privilege database access controls.
- 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-13525 — 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-13525 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