dbcve.org
InjectionWeakness · CWE-74

CVE-2026-5564

HIGH · 7.3 CVSS v3.1 Published 2026-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 code-projects Simple Laundry System 1.0. Affected by this vulnerability is an unknown functionality of the file /searchguest.php of the component Parameter Handler. This manipulation of the argument searchServiceId causes sql injection. The attack may 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 · moderate confidence

SQL injection vulnerability in Simple Laundry System 1.0's /searchguest.php file allows remote attackers to inject malicious SQL queries via the searchServiceId parameter. The lack of input sanitization or parameterized queries in the Parameter Handler component enables attackers to manipulate database queries.

MitigationImplement parameterized queries or prepared statements for all database interactions, particularly in the searchServiceId parameter handler. Apply input validation and escaping as an additional defense layer.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Simple Laundry System installation
    Check if the Simple Laundry System application is installed on the server. Look for the web root directory containing /searchguest.php or check the application's file structure for laundry management related files.
    Affected if The application is installed and contains searchguest.php in the web accessible directory.
  2. Identify installed version
    Check the application's version. Look for version information in README files, about pages, or configuration files within the Simple Laundry System installation directory.
    Affected if The installed version is Simple Laundry System 1.0.
  3. Locate vulnerable script
    Verify the presence of /searchguest.php in the web application's directory structure. Check the searchServiceId parameter handling within this file.
    Affected if The file /searchguest.php exists and accepts the searchServiceId parameter without sanitization.
  4. Test parameter vulnerability
    If the application is accessible, send a crafted request to /searchguest.php with the searchServiceId parameter containing SQL injection payloads (e.g., searchServiceId=1' OR '1'='1). Observe if the application returns unexpected database errors or behaves differently.
    Affected if The searchServiceId parameter directly concatenates user input into SQL queries without parameterization or input validation.
  5. Check for parameterized queries
    Examine the source code of /searchguest.php. Search for SQL query construction that uses the searchServiceId parameter. Look for prepared statements, parameterized queries, or input validation functions.
    Affected if The code uses direct string concatenation for the searchServiceId parameter in SQL statements rather than parameterized queries.

A user is affected if Simple Laundry System version 1.0 is installed and the /searchguest.php script uses direct SQL concatenation with the searchServiceId parameter.

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 parameterized queries or prepared statements for all database interactions, particularly in the searchServiceId parameter handler. Apply input validation and escaping as an additional defense layer.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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