Skip to main content
Menu
CVEs

Neotroni Lighting PowerLink unauthenticated database read via SQL injection

Affects Neotroni Lighting PowerLink V1.1. CVSS scores it 8.7 (high). Fixed in version 2.0 or later.

CVE-2026-133534Published , updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.0 or later
Who is exposed
Not reported

Summary

PowerLink from Neotroni Lighting has a SQL injection flaw that lets an unauthenticated attacker remotely send crafted SQL commands and read contents of the database. The attacker needs no login and no action from a user.

Written by a model

Original description

PowerLink developed by Neotroni Lighting has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read database contents.

Who should check

Teams running Neotroni Lighting PowerLink smart street light management system V1.1 and earlier

“PowerLink V1.1”

twcert.org.tw

What to do

Upgrade to a fixed version: 2.0 or later.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133534 (Neotroni Lighting|PowerLink - SQL Injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133534 (entry last updated 2026-11-20):
Affected:
- Neotroni Lighting PowerLink: versions 1.1
Fixed versions: 2.0 or later.
Conditions (all must be true for the bug to be hit):
- Running Neotroni Lighting PowerLink V1.1 (source: https://www.twcert.org.tw/en/cp-139-11424-ecbad-2.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133534 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133534 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.twcert.org.tw/tw/cp-132-11423-cb8d4-1.html
- https://www.twcert.org.tw/en/cp-139-11424-ecbad-2.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133534
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133534"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133534
RecordNVD · CVE-2026-133534
Other links 2
Linktwcert.org.tw · tw/cp-132-11423-cb8d4-1.html
Linktwcert.org.tw · en/cp-139-11424-ecbad-2.html

Questions about CVE-2026-133534

Is CVE-2026-133534 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The flaw lets an attacker inject arbitrary SQL commands into PowerLink, which can be used to read the contents of its database.

Source: twcert.org.tw

Which versions are affected by CVE-2026-133534?

PowerLink: version 1.1.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory names PowerLink V1.1 as the affected version. To check a installation, look at the PowerLink version it reports in its own interface or package information.

Source: twcert.org.tw

How do I fix CVE-2026-133534?

Update PowerLink to version 2.0 or later, which the vendor states is the fixed release.

Source: twcert.org.tw

No corrections so far. Something wrong on this page? Report an error.