CVE-2026-13559
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 weakness has been identified in code-projects Real State Services 1.0. Impacted is an unknown function of the file /single-list_sale.php?action=add. Executing a manipulation of the argument ID can lead to sql injection. The attack can be executed 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 confidenceA SQL injection vulnerability exists in the Real State Services 1.0 application. The vulnerability is located in the ID parameter of /single-list_sale.php?action=add, allowing remote attackers to manipulate SQL queries through the unparameterized input.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Real State Services 1.0 is installedLocate the application version by checking the readme.txt, changelog, or admin panel. Search for files like README.md, version.php, or check the footer of the web interface for version text.Affected if The installed application is Real State Services version 1.0
-
Verify the vulnerable script existsCheck if the file /single-list_sale.php exists in the web root directory by attempting to access it via HTTP request or listing the directory contents.Affected if The file single-list_sale.php is present in the web-accessible directory
-
Confirm the action parameter is presentRequest /single-list_sale.php?action=add and verify the page loads without a 404 error.Affected if The endpoint responds with content rather than a not found error
-
Inspect the ID parameter handling in source codeExamine the PHP source code of single-list_sale.php and locate the code handling the 'id' GET parameter. Search for SQL queries that incorporate this parameter without using prepared statements or parameter binding.Affected if The code contains SQL queries that directly concatenate or insert the ID parameter into query strings without escaping or parameterization
-
Check database query implementationReview all database queries in single-list_sale.php that involve the ID parameter. Verify whether they use PDO prepare(), mysqli prepare(), or other parameterized query methods.Affected if SQL queries use the ID parameter in string concatenation or interpolation rather than bound parameters
A user is affected if they are running Real State Services 1.0 and the single-list_sale.php file handles the ID parameter without parameterized queries.
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 dataThe SQL injection should be remediated by replacing dynamic SQL queries with parameterized queries or prepared statements, implementing proper input validation on the ID parameter, and applying the principle of least privilege to the database user account.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13559 — 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-13559 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