HIGH 7.3

CVE-2026-14745: SQL Injection in Real State Services 1.0 – Remote Code Execution Risk

A SQL injection vulnerability exists in code-projects Real State Services version 1.0 that allows unauthenticated attackers to manipulate the ID parameter in the /single-list_rent.php file, potentially exposing or altering sensitive data in the underlying database. The vulnerability can be exploited remotely without authentication, and proof-of-concept code is publicly available, increasing the risk of active exploitation.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-74, CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-07-05 / 2026-07-06

NVD description (verbatim)

A weakness has been identified in code-projects Real State Services 1.0. This impacts an unknown function of the file /single-list_rent.php. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14745 is a SQL injection flaw (CWE-89) stemming from improper neutralization of special elements (CWE-74) in the ID parameter of /single-list_rent.php. The vulnerability lacks authentication controls (PR:N) and has low attack complexity (AC:L), meaning an attacker can craft malicious SQL payloads and submit them via the network to execute arbitrary database queries. The CVSS 3.1 score of 7.3 (HIGH) reflects low confidentiality, integrity, and availability impact within the scope of a single user context, though in real estate applications handling customer data, the practical impact could be significant.

Business impact

Real Estate Services deployments using version 1.0 face risk of unauthorized access to property listings, customer information, and potentially financial or transaction records stored in the backend database. Attackers could extract sensitive data, modify listings, or corrupt records. The public availability of exploit code elevates the likelihood of opportunistic attacks. Organizations hosting this software should assume elevated exposure given the ease of remote exploitation and lack of authentication requirements.

Affected systems

code-projects Real State Services 1.0 is the confirmed affected product. Any deployment or installation of this specific version running /single-list_rent.php is vulnerable. Verify your installed version against vendor advisories and check whether you are running version 1.0 or a patched release.

Exploitability

Exploitability is high. The attack vector is network-based with no authentication required, no user interaction needed, and low complexity—an attacker can exploit this with a simple HTTP request containing a malicious ID parameter. Public exploit availability further lowers the barrier to exploitation, making this a practical attack vector for both targeted and indiscriminate attacks against exposed instances.

Remediation

Immediate action is required: upgrade code-projects Real State Services to a patched version released after this vulnerability disclosure. Verify the patch version against the vendor advisory. As an interim measure, implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns in the ID parameter, restrict network access to the affected application, and monitor database logs for suspicious query patterns.

Patch guidance

Contact code-projects for the official patch or security update for Real State Services. The vendor should provide a version number addressing this SQL injection. Verify the patch version in the official advisory before deployment. Test the patch in a non-production environment first, then deploy across all instances running version 1.0. Document your patching completion and version numbers for compliance records.

Detection guidance

Monitor web server logs and WAF logs for requests to /single-list_rent.php containing SQL syntax characters (single quotes, double dashes, UNION, SELECT, etc.) in the ID parameter. Monitor database logs for unusual query patterns, failed authentication attempts, or unexpected data access. Use intrusion detection signatures for SQL injection attacks. Implement query-level logging to capture potentially malicious SQL statements before execution.

Why prioritize this

This vulnerability warrants immediate prioritization due to: (1) HIGH CVSS score (7.3) with multiple impact vectors; (2) remote unauthenticated exploitation with low attack complexity; (3) public exploit availability creating immediate attack risk; (4) sensitivity of real estate and customer data typically handled by such systems; and (5) likelihood that opportunistic scanning and exploitation are already underway. Patch or implement compensating controls within days, not weeks.

Risk score, explained

The CVSS 3.1 score of 7.3 reflects a network-accessible SQL injection with no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N). The 'S:U' (scope unchanged) and 'C:L/I:L/A:L' (low impact across confidentiality, integrity, and availability) yield a HIGH severity rating. However, in the context of a real estate application storing PII and transaction data, the practical risk is elevated—SQL injection often permits complete database compromise, meaning the assigned impact metrics may understate actual organizational risk.

Frequently asked questions

Do we need to patch immediately if we are not running Real State Services version 1.0?

Verify your installed version against the vendor advisory. If you are running a version released after the initial vulnerability disclosure (2026-07-05) or a version explicitly patched by the vendor, you may not be vulnerable. However, do not assume; check the vendor's security advisory for the specific patched versions.

What is the difference between CWE-74 and CWE-89 here?

CWE-89 is SQL Injection—the specific, exploitable flaw. CWE-74 (Improper Neutralization of Special Elements in Output) is the broader weakness category describing the root cause: the application fails to sanitize or parameterize user input before using it in SQL queries. Understanding both helps identify similar risks in your codebase.

Is this vulnerability in the CISA Known Exploited Vulnerabilities (KEV) catalog?

No, this vulnerability is not listed in the CISA KEV catalog as of the last update. However, public exploit code is available, which means exploitation is likely occurring in the wild. Do not rely on KEV listing as your sole signal for urgency; immediate patching is still critical.

Can a Web Application Firewall fully mitigate this vulnerability?

A WAF can reduce attack surface by blocking obvious SQL injection patterns in the ID parameter, but it is not a permanent solution and can be bypassed with obfuscation or encoding techniques. WAF rules should be treated as a temporary compensating control while you work toward patching the application code itself.

This analysis is provided for informational purposes to assist security professionals in risk assessment and remediation planning. The vulnerability details, CVSS score, and affected product information are sourced from published CVE data and vendor advisories. Patch version numbers, vendor contact information, and detailed advisory links should be verified directly with code-projects' official security advisories before deployment. This explainer does not constitute legal or compliance advice. Organizations should validate applicability to their environment and consult with their security and legal teams regarding disclosure, patch timelines, and regulatory obligations. SEC.co makes no warranty regarding the completeness or accuracy of patch availability or vendor response timelines. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).