Skip to main content
VulnerabilityPublished

CVE-2026-133611: vulnerability-lookup prior to version 7.1.0 contains two security issues in its web interface

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133611· Medium 4.6

Not known to be exploited · CVSS 4.6 Medium · fixed in 7.1.0 : update vulnerability-lookup when convenient.

Data as of 20 Nov 2026, 11:05 UTC

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

Thin evidence

One scorer or none
CVSS scores by source
CNA (CIRCL)CVSS 4.04.6
Patch
Available – fixed in 7.1.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
vulnerability-lookupvulnerability-lookupAffected
  • ≥ <7.1.0, < 7.1.0
Fixed in–

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

AI-suggested

A fix is available in version 7.1.0, which addresses these issues. Users should upgrade to version 7.1.0 or later to remediate these vulnerabilities. Until upgrading, avoid exposing users to untrusted content that could trigger the GET request to disable 2FA, and restrict access to unpublished comment URLs. No vendor advisory or patch links were provided, so verify with the vendor for official remediation details.

Description

vulnerability-lookup versions prior to 7.1.0 have two security issues in the web interface. The first allows disabling two-factor authentication (2FA) via a GET request to /user/toggle_2fa without password confirmation or CSRF protection, enabling attackers to trick users into disabling 2FA by viewing crafted content. The second issue exposes unpublished comments on the comment detail page to anyone with the URL, bypassing intended moderation controls. These issues combined can degrade account security and leak unapproved content.

References

Community reviews

Loading reviews…