dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15523

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 weakness has been identified in CodeAstro Simple Online Leave Management System 1.0. Affected by this issue is some unknown functionality of the file /SimpleOnlineLeave/admin/dashboard.php. This manipulation of the argument Name causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks.

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 confidence

SQL injection vulnerability in CodeAstro Simple Online Leave Management System 1.0 allows remote attackers to manipulate the 'Name' parameter in /SimpleOnlineLeave/admin/dashboard.php to inject malicious SQL queries. The vulnerability stems from unsanitized user input being directly incorporated into SQL statements without parameterized queries or proper input validation.

MitigationImplement prepared statements/parameterized queries for all database interactions involving user-supplied input in dashboard.php. Apply input validation and sanitize the 'Name' parameter before using it in SQL 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 checks

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

  1. Locate the application installation directory
    Search for the 'SimpleOnlineLeave' folder in the web server's document root (commonly /var/www/html, /www, or C:\inetpub\wwwroot on Windows servers)
    Affected if The directory SimpleOnlineLeave exists on the server
  2. Verify the vulnerable file exists
    Check for the presence of /SimpleOnlineLeave/admin/dashboard.php in the web root
    Affected if The file dashboard.php exists in the admin subdirectory
  3. Confirm the application version
    Review any version file, README, or about page within the SimpleOnlineLeave installation for version 1.0
    Affected if The installed version is 1.0
  4. Inspect the Name parameter handling in dashboard.php
    Open dashboard.php and locate the SQL query that uses the 'Name' parameter - search for 'Name' in the code to find the vulnerable query
    Affected if The code contains a SQL query incorporating the 'Name' parameter without using prepared statements, parameterized queries, or input sanitization functions such as htmlspecialchars, mysqli_real_escape_string, or PDO::quote

If the CodeAstro Simple Online Leave Management System version 1.0 is installed with the dashboard.php file present and the 'Name' parameter is used in raw SQL queries without sanitization or prepared statements, the environment is affected by CVE-2026-15523.

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

Implement prepared statements/parameterized queries for all database interactions involving user-supplied input in dashboard.php. Apply input validation and sanitize the 'Name' parameter before using it in SQL queries.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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