Skip to main content
VulnerabilityPublished

CVE-2026-134623: Microweber · CWE-266

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134623· Medium 6.9

Public exploit available · CVSS 6.9 Medium · fixed in 2.0.21 : patch Microweber as a priority.

Data as of 22 Nov 2026, 07:26 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.06.9
CNA (VulDB)CVSS 3.17.3
CNA (VulDB)CVSS 3.07.3
CNA (VulDB)CVSS 2.07.5
Patch
Available – fixed in 2.0.21
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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
MicroweberAffected
  • 2.0.0 – 2.0.20
21 affected builds
Fixed in–
GitHubmicroweber/microweberpkg:github/microweber/microweberOther threatsAffected
  • <=2.0.20
Fixed in–

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

AI-suggested

Upgrade Microweber to version 2.0.21 or later, which contains the official fix for this vulnerability (patch e639d26e61b989b100f8b6f6bb78c0cecca79b99). No other mitigations are indicated.

Description

A vulnerability in Microweber up to version 2.0.20 allows improper access control due to a flaw in the UserManager::make_logged function within the Generic API Dispatcher component. This flaw can be exploited remotely without authentication. The issue is fixed in version 2.0.21.

References

Community reviews

Loading reviews…