CVE-2026-14743
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 vulnerability was identified in code-projects Real State Services 1.0. The impacted element is an unknown function of the file /normalHomeSale.php. Such manipulation of the argument loc leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might be used.
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 confidenceSQL injection vulnerability in the loc parameter of /normalHomeSale.php in code-projects Real State Services 1.0 allows remote attackers to inject arbitrary SQL commands through unsanitized user 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 installationLocate the web application files and check for the presence of normalHomeSale.php in the web root or application directory. Verify the application is code-projects Real State Services version 1.0.Affected if The file normalHomeSale.php exists and the application is Real State Services 1.0
-
Identify the loc parameter handlerOpen normalHomeSale.php and search for code that processes the 'loc' parameter from user input (e.g., $_GET['loc'] or $_POST['loc']).Affected if The loc parameter is retrieved from user input without sanitization
-
Check SQL query constructionExamine how the loc parameter value is used in SQL queries within normalHomeSale.php. Look for direct string concatenation or string interpolation in SQL statements.Affected if SQL queries are built by concatenating the loc parameter directly into the query string without using prepared statements or parameter binding
-
Verify parameter binding is absentSearch for 'prepare', 'bindParam', 'bindValue', or 'parameterized' in the file. Confirm whether the SQL query uses placeholder parameters.Affected if No prepared statements or parameter binding are used for the loc parameter in SQL queries
-
Test parameter injection potentialIf the application is accessible, submit a request to normalHomeSale.php with a test value in the loc parameter (e.g., 'loc=test') and observe if the application responds without SQL errors or unexpected behavior.Affected if The application accepts and processes unsanitized input in the loc parameter
A user is affected if they are running code-projects Real State Services 1.0 with the normalHomeSale.php file present and the loc parameter is processed in SQL queries without prepared statements or input sanitization.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the loc parameter in normalHomeSale.php to prevent SQL injection.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14743 — 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-14743 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