dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15558

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 CodeAstro Simple Online Leave Management System 1.0. Affected by this issue is some unknown functionality of the file /SimpleOnlineLeave/admin/deletemp.php. Such manipulation of the argument ID leads to sql injection. The attack can be executed 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 CodeAstro Simple Online Leave Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /SimpleOnlineLeave/admin/deletemp.php. The lack of input sanitization or parameterized queries in the delete employee functionality enables attackers to manipulate SQL statements.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the ID parameter in deletemp.php. Also audit other admin files for similar SQL injection vulnerabilities.

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 checks

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

  1. Verify the application is installed
    Search for the CodeAstro Simple Online Leave Management System web directory on your server, typically found at /SimpleOnlineLeave/ or check your web root for this folder
    Affected if The application directory exists on the server
  2. Confirm the version number
    Check for version indicators in the application, such as a version.php file, README file, footer content, or any admin/about page that displays the software version
    Affected if The installed version is 1.0
  3. Locate the vulnerable file
    Check if the file /SimpleOnlineLeave/admin/deletemp.php exists on the web server
    Affected if The file deletemp.php exists in the admin directory
  4. Verify admin access is enabled
    Confirm the /SimpleOnlineLeave/admin/ directory is accessible via the web server and that admin credentials can be obtained or are already configured
    Affected if The admin panel is accessible without additional authentication barriers preventing access to deletemp.php
  5. Inspect the SQL query in deletemp.php
    Open deletemp.php and examine the code around line where the ID parameter is used in SQL queries. Look for direct insertion of the ID parameter into SQL statements without using prepared statements, parameterized queries, or input sanitization functions like mysqli_real_escape_string or PDO::prepare
    Affected if The code shows the ID parameter being directly concatenated or inserted into SQL queries without parameterized query implementation

Your environment is affected if CodeAstro Simple Online Leave Management System version 1.0 is installed, the file deletemp.php exists, and code inspection reveals the ID parameter is used directly in SQL queries without prepared statements or sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the ID parameter in deletemp.php. Also audit other admin files for similar SQL injection vulnerabilities.

Recommended fix Moderate confidence
  1. 1. Locate and backup the file /SimpleOnlineLeave/admin/deletemp.php.
  2. 2. Open deletemp.php and replace any concatenated SQL query with a parameterized query (e.g., use PDO or MySQLi with placeholders).
  3. 3. Ensure the ID parameter is safely cast to an integer before inclusion in the query, for example: $id = intval($_GET['ID']);
  4. 4. Apply input validation: verify that the sanitized ID meets expected format (e.g., only digits).
  5. 5. Protect the admin directory by enforcing authentication, session checks, and optionally IP restrictions (e.g., via .htaccess or web server config).
  6. 6. If the deletemp functionality is not required, remove or rename the script to prevent any access.
  7. 7. Test the modified script to confirm the SQL injection vector is eliminated.
  8. 8. Monitor logs for any suspicious activity targeting deletemp.php.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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