LiveActive security incident?Get immediate response
CVE Record

CVE-2026-15498: sergomanov SmartHomeAdatum Login users.php sql injection

A vulnerability was identified in sergomanov SmartHomeAdatum up to cf495353d81b680675eb8d9aa14a318aa45ce12c. This impacts an unknown function of the file users.php of the component Login. Such manipulation of the argument Login leads to sql injection. The attack may be launched remotely. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The vendor was contacted early about this disclosure but did not respond in any way.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-15498 is a remotely reachable SQL injection in SmartHomeAdatum’s login component. An unauthenticated attacker may manipulate the Login argument in users.php, potentially affecting database confidentiality, integrity, and availability. Public sources do not name a fixed release, and the vendor reportedly did not respond.

Executive priority

Prioritize review of any internet-facing SmartHomeAdatum deployment. The vulnerability affects login and could compromise stored data. Urgency is high, but evidence is incomplete because no fixed version, vendor advisory, or confirmed exploitation is currently cited.

Technical view

The reported flaw affects sergomanov SmartHomeAdatum up to commit cf495353d81b680675eb8d9aa14a318aa45ce12c. VulDB maps it to CWE-89 and CWE-74, with CVSS 2.0 score 7.5: AV:N/AC:L/Au:N/C:P/I:P/A:P. The product uses rolling releases, so affected and fixed version boundaries are not clearly documented.

Likely exposure

Exposure is most likely where SmartHomeAdatum is deployed with its login interface reachable over a network, especially from the internet. Because the report identifies unauthenticated remote attack conditions, public-facing instances should be treated as higher priority.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. VulDB states remote exploitation is possible, but available public sources do not provide validated exploit activity details. Treat this as a serious exposure issue, not as confirmed in-the-wild exploitation.

Researcher notes

The public record is sparse and primarily VulDB-derived. Key gaps include exact vulnerable code path, fixed commit, vendor confirmation, and exploit telemetry. Avoid assuming all forks or unrelated smart-home products are affected without matching SmartHomeAdatum and the cited commit lineage.

Mitigation direction

  • Check the upstream repository or vendor channels for any commit or guidance after cf495353d81b680675eb8d9aa14a318aa45ce12c.
  • Restrict network access to SmartHomeAdatum login pages to trusted users or internal networks.
  • Place compensating controls in front of the login interface where feasible.
  • Monitor application and database logs for abnormal login parameter activity.
  • Prioritize replacement or hardening if no maintained fix is available.

Validation and detection

  • Inventory SmartHomeAdatum deployments and identify their deployed commit or source snapshot.
  • Confirm whether users.php and the Login component are reachable remotely.
  • Review application code for parameterized handling of the Login argument.
  • Check logs for suspicious login requests or database errors around users.php.
  • Track CVE and VulDB pages for updated fix or exploitation information.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-15498 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
0ADP providers
5Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 2.0HighAV:N/AC:L/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:UR106.4VulDB
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:R3.93.4VulDB
7.3CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:R3.93.4VulDB
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X——VulDB

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-15498Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
sergomanovSmartHomeAdatumcf495353d81b680675eb8d9aa14a318aa45ce12cListed
Weakness

CWE details

CWE-74CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.