CVE-2026-14768
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. This vulnerability affects unknown code of the file /builderHome.php. This manipulation of the argument loc causes sql injection. The attack is possible to be carried out 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 · high confidenceSQL injection vulnerability in the 'loc' parameter of builderHome.php in code-projects Real State Services 1.0 allows remote attackers to inject malicious SQL queries. The vulnerable parameter is not properly sanitized or parameterized, enabling attackers to manipulate database queries. This is a high-severity (CVSS 7.3) remote vulnerability with publicly available exploit code.
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 installationLocate the application root directory and verify the presence of files typical to the code-projects Real State Services 1.0 application. Check for files such as builderHome.php in the web root or application directories.Affected if The code-projects Real State Services 1.0 application is present on the server
-
Identify the vulnerable fileSearch for the file 'builderHome.php' within the application directory structure. This is the specific file containing the SQL injection vulnerability.Affected if builderHome.php exists in the web-accessible directory
-
Verify the 'loc' parameter is usedExamine the builderHome.php source code and identify if the 'loc' parameter is processed. Search for code that retrieves the 'loc' parameter from GET or POST requests and incorporates it into SQL queries without prepared statements or proper sanitization.Affected if The 'loc' parameter is received from user input and used in SQL queries without parameterized queries or input sanitization
-
Check database interaction methodReview the database connection and query execution code within builderHome.php. Look for patterns where user input from the 'loc' parameter is directly concatenated or interpolated into SQL strings, rather than being passed as bound parameters.Affected if SQL queries involving the 'loc' parameter are constructed using string concatenation or interpolation rather than prepared statements
The environment is affected if code-projects Real State Services 1.0 is installed and builderHome.php contains code that passes the 'loc' parameter directly into SQL queries without using prepared statements or parameter binding.
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 dataImplement prepared statements/parameterized queries for all database operations involving user input, particularly the 'loc' parameter. Additionally, apply input validation and output encoding as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14768 — 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-14768 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