dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-3321

HIGH · 8.7 CVSS v4.0 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability of authorization bypass through user-controlled key in the 'console-survey/api/v1/answer/{EVENTID}/{TIMESTAMP}/' endpoint. Exploiting this vulnerability would allow an unauthenticated attacker to enumerate event IDs and obtain the complete Q&A history. This publicly exposed data may include IDs, private URLs, private messages, internal references, or other sensitive information that should only be exposed to authenticated users. In addition, the leaked content could be exploited to facilitate other malicious activities, such as reconnaissance for lateral movement, exploitation of related systems, or unauthorised access to internal applications referenced in the content of chat messages.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an IDOR (Insecure Direct Object Reference) authorization bypass vulnerability in the console-survey API endpoint at '/console-survey/api/v1/answer/{EVENTID}/{TIMESTAMP}/'. The endpoint fails to properly validate user authorization before returning Q&A history data, allowing any unauthenticated attacker to access sensitive survey responses by manipulating event ID values.

MitigationImplement proper authentication and authorization checks on the affected endpoint to ensure only authenticated users with valid permissions can access Q&A history data. Consider implementing rate limiting to prevent enumeration attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if console-survey component is deployed
    Review application architecture documentation or scan for '/console-survey' path in web server configurations and deployed web applications
    Affected if The console-survey API component is present in the environment
  2. Verify the vulnerable endpoint exists
    Test for the presence of '/console-survey/api/v1/answer/' endpoint by sending a GET request with any placeholder values for EVENTID and TIMESTAMP (e.g., /console-survey/api/v1/answer/test/1234567890/)
    Affected if The endpoint responds with HTTP 200 or other valid responses (not 404)
  3. Confirm authorization bypass exists
    Send unauthenticated HTTP GET requests to the endpoint with different EVENTID values and observe if Q&A history data is returned without requiring login credentials or session tokens
    Affected if The endpoint returns survey response data without any authentication token or session validation
  4. Check for improper event ID validation
    Attempt to access multiple different EVENTID values without authentication and verify that the system returns data for various events without checking user permissions
    Affected if Different EVENTID values return corresponding survey data without authorization checks
  5. Verify sensitive data exposure
    Analyze responses from the endpoint to confirm Q&A history containing potentially sensitive survey responses is accessible to unauthenticated users
    Affected if The API returns actual survey question and answer content without verifying the requester has permission to view that data

The environment is affected if the console-survey API endpoint at '/console-survey/api/v1/answer/{EVENTID}/{TIMESTAMP}/' is accessible and returns Q&A history data to unauthenticated users without performing authorization validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks on the affected endpoint to ensure only authenticated users with valid permissions can access Q&A history data. Consider implementing rate limiting to prevent enumeration attacks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3321 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data