vulnerability-lookup: 2FA Disabled via Unauthenticated GET Request and Unpublished Comments Accessible Without Authorization
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| vulnerability-lookup | vulnerability-lookup | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
The /user/toggle_2fa endpoint is restricted to POST only, enabling CSRF token validation, and now requires the user's password to confirm disabling of 2FA. The comment detail view now checks the comment's publication status and returns 404 for unpublished comments unless the requester is the author or holds moderator privileges, matching the existing API behavior.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vulnerability-lookup prior to version 7.1.0 contains two security issues in its web interface. First, the /user/toggle_2fa 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. | |
| Title | vulnerability-lookup: 2FA Disabled via Unauthenticated GET Request and Unpublished Comments Accessible Without Authorization | |
| First Time appeared |
Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup |
|
| Weaknesses | CWE-306 CWE-352 CWE-862 |
|
| CPEs | cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup |
|
| References |
| |
| Metrics |
cvssV4_0
|
No data.
No data.
No data.
No data.