CVE-2026-133611: vulnerability-lookup: 2FA Disabled via Unauthenticated GET Request and Unpublished Comments Accessible Without Authorization

Published Nov 20, 2026
·
Updated

vulnerability-lookup prior to version 7.1.0 contains two security issues in its web interface. First, the /user/toggle2fa endpoint accepted HTTP GET requests and disabled the authenticated user's two-factor authentication without requiring password confirmation. Because the state-changing operation was reachable via GET, an attacker with a basic account could embed an image element (or any other GET-triggering markup) in a comment pointing to that endpoint. When a victim with 2FA enabled viewed the comment, their browser silently issued the GET request, disabling the victim's second factor of authentication. No CSRF token was enforced on the GET path, and no password was required to confirm the action. Second, the comment detail page (/comment/<uuid>) rendered unpublished comments to any visitor who possessed the URL, bypassing the moderation workflow that was intended to keep such content hidden until approved. The API correctly restricted access, but the web view did not enforce the same authorization check. The combined effect allows an attacker to degrade a victim's account security (removal of 2FA) through a single page view and to read content that was not yet approved for public release.

Affected Software

1 affected component
Circl Vulnerability-Lookup<7.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade vulnerability-lookup to a version that resolves this vulnerability.

    Fixed in 7.1.0

Event History

Nov 20, 2026
CVE Published
via MITRE·07:17 AM
Data Sourced
via MITRE·07:17 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·07:17 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments of vulnerability-lookup before version 7.1.0 are affected. The issues are in the web interface: the 2FA toggle endpoint and the browser-rendered comment detail page.

2

What does an attacker need to disable another user's 2FA?

The attacker needs a basic account that can post or otherwise place GET-triggering markup in a comment, and the target must have 2FA enabled and view that content while authenticated. No CSRF token or password confirmation was required for the affected GET request.

3

Who can view an unpublished comment under the affected behavior?

Any visitor possessing the unpublished comment's detail URL could view it through the web page. This did not require authorization, although the API correctly restricted access.

4

How can I check whether I am exposed?

Confirm whether the deployed version is earlier than 7.1.0. In an affected installation, test whether an authenticated GET request to /user/toggle_2fa disables 2FA without CSRF validation or password confirmation, and whether an unauthenticated visitor can open /comment/<uuid> for an unpublished comment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203