dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14744

HIGH · 7.3 CVSS v3.1 Published 2026-07-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 7 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 flaw has been discovered in code-projects Real State Services 1.0. This affects an unknown function of the file /normalHomeRent.php. Performing a manipulation of the argument loc results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may 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 the loc parameter of /normalHomeRent.php in code-projects Real State Services 1.0 allows remote attackers to manipulate SQL queries via unsanitized user input.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation for the loc parameter. Apply vendor patch if available.

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. Identify if Real State Services 1.0 is installed
    Search the web root directory for the file normalHomeRent.php or the presence of a 'Real State Services' application directory
    Affected if The application code-projects Real State Services is present on the server
  2. Check the application version
    Look for a version file, readme, or check the software metadata to confirm version 1.0
    Affected if The installed version is 1.0 of Real State Services by code-projects
  3. Locate the vulnerable PHP file
    Find normalHomeRent.php in the web application directory structure
    Affected if The file normalHomeRent.php exists in the application
  4. Inspect the loc parameter handling
    Open normalHomeRent.php and search for code that uses the 'loc' parameter in SQL queries without parameterized queries or input sanitization
    Affected if The 'loc' parameter is used directly in SQL statements without prepared statements, escaping, or validation
  5. Test the parameter for SQL injection
    Using a safe testing method, send a crafted 'loc' parameter value (such as a single quote) to normalHomeRent.php and observe if SQL errors are returned or behavior changes
    Affected if The application returns SQL error messages or exhibits unexpected behavior when special characters are passed in the loc parameter

The environment is affected if code-projects Real State Services version 1.0 is installed and the normalHomeRent.php file contains direct use of the loc parameter in SQL queries without parameterized queries or input validation.

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

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation for the loc parameter. Apply vendor patch if available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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