Skip to main content
VulnerabilityPublished

CVE-2026-66751: sdelements lets-chat · Missing Authorization

Affects sdelements lets-chatSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
sdelementslets-chatAffected
  • >=0.3.0 <=0.4.8
Fixed in–
GitHublets-chatpkg:github/lets-chatOther threatsAffected
  • >=0.3.0 <=0.4.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor vendor advisories for updates. Until a fix is available, restrict authenticated user permissions carefully and consider limiting access to the rooms deletion functionality. Prepare for potential manual recovery by backing up the database regularly.

Description

Let's Chat 0.3.0 through 0.4.8 contains an improper authorization vulnerability that allows any authenticated user to archive any room on the server by sending a DELETE request to the rooms handler without ownership verification. Attackers can enumerate room IDs via the rooms listing endpoint and permanently archive private or password-protected rooms they cannot access, with no application-level recovery path requiring direct database intervention to restore.

References

Community reviews

Loading reviews…