Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71264 – Authentication Bypass / Missing Authorization – WLED (all versions)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71264 is a missing authorization vulnerability (CWE-862) in WLED, the open-source ESP8266/ESP32 LED-control firmware. The GET /json/cfg endpoint exposes device configuration without a settings-PIN check, and the PIN unlock state is tracked in a global boolean rather than per session, so any successful unlock grants configuration-write access to all subsequent clients until reboot. It carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: The serveJson() handler in wled00/wled_server.cpp processes configuration requests with no settings-PIN check, unlike the /edit endpoint which explicitly validates correctPIN.
  • Secondary flaw: PIN unlock state is stored as a global boolean flag instead of per-session state, so once any client submits the correct PIN, the device stays unlocked for every client until it reboots.
  • Trigger conditions: An unauthenticated request to GET /json/cfg returns device configuration; the persistent unlock state then extends write access to other clients.
  • Attack vector: Network, low complexity, no privileges and no user interaction required.
  • Impact: Disclosure of device configuration and write access enabling firmware updates, WiFi reconfiguration, and factory resets.

Affected software

  • WLED (vendor: Aircoookie) — all versions.

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: Monitor the WLED project for a fixed release and upgrade as soon as a patched firmware version is published.
  • If no patch: Do not expose WLED devices directly to the internet. Place them on an isolated/segmented network (VLAN), restrict access to the web and JSON API with firewall rules or a reverse proxy requiring authentication, and reboot devices to clear any persisted unlock state.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: WLED
  • Raw response body: Loading WLED UI..., Reboot WLED, WLED instances, WLED is receiving live, localStorage.getItem("wledPmt"), localStorage.getItem("wledPalx"), prompt("File Mode. Please enter WLED IP!")

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge