dbcve.org
Core FirmwareOperating system · Taphome

CVE-2023-2760

HIGH · 7.6 CVSS v3.1 Published 2023-07-17
Fix available
A fix is available. Upgrade to 2023.2 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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
An SQL injection vulnerability exists in TapHome core HandleMessageUpdateDevicePropertiesRequest function before version 2023.2, allowing low privileged users to inject arbitrary SQL directives into an SQL query and execute arbitrary SQL commands and get full reading access. This may also lead to limited write access and temporary Denial-of-Service.

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 TapHome core's HandleMessageUpdateDevicePropertiesRequest function allows low-privileged authenticated users to inject arbitrary SQL directives into queries, enabling full database read access, limited write access, and potential temporary denial of service.

MitigationUpgrade to TapHome version 2023.2 or later to obtain the patch. If immediate upgrade is not feasible, implement proper input validation and parameterized queries in the affected function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Core FirmwareOperating system
Affected:< 2023.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 TapHome Core installation
    Locate the TapHome Core device or service on your network and determine its firmware version. This is typically found in the device's web interface, admin panel, or system information page.
    Affected if Unable to determine the version or version is unknown
  2. Verify firmware version against affected range
    Compare your installed TapHome Core Firmware version to the affected range. The vulnerability affects versions prior to 2023.2.
    Affected if Installed version is below 2023.2
  3. Confirm authentication is enabled
    Check if user authentication is enabled on the TapHome Core system. The vulnerability requires an authenticated user session to exploit the SQL injection in HandleMessageUpdateDevicePropertiesRequest.
    Affected if Authentication is enabled and user accounts exist
  4. Assess network exposure
    Determine if the TapHome Core interface is accessible from the network. Since the flaw can be exploited by low-privileged authenticated users, check whether remote access or network-exposed management interfaces are enabled.
    Affected if Remote network access to the TapHome Core interface is enabled

You are affected if your TapHome Core Firmware version is below 2023.2 and authentication is enabled on a network-accessible instance.

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.

dbcve · scoped
Upgrade available Upgrade to 2023.2 or later
Fixed in 2023.2
Interim mitigation

Upgrade to TapHome version 2023.2 or later to obtain the patch. If immediate upgrade is not feasible, implement proper input validation and parameterized queries in the affected function.

Recommended fix Moderate confidence

2023.2

  1. Verify current TapHome Core Firmware version by accessing the device management interface
  2. Download TapHome Core Firmware version 2023.2 or later from the official TapHome vendor website
  3. Review upgrade documentation for any pre-upgrade requirements such as backup procedures
  4. Perform the firmware upgrade following the vendor's recommended upgrade procedure
  5. After upgrade, verify the system is operational and the vulnerability is resolved
  6. Consider changing credentials as a precautionary measure given the SQL injection exposure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Core Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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