CVE-2026-12863
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 · uneditedAn unvalidated redirect was contained in Venueless' social login functionality and could be exploited for phishing using trusted domains.
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 · moderate confidenceThis is an open redirect vulnerability in Venueless' social login feature where the application fails to validate redirect URLs before forwarding users after authentication. Attackers can craft malicious links using trusted domains (e.g., venueless.example.com) that appear legitimate but redirect users to attacker-controlled sites, enabling phishing 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
- Low
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Venueless installationLocate the Venueless application in your environment by checking for its web application files, Docker containers, or service processes listening on configured ports.Affected if Venueless software is present in the environment
-
Determine Venueless versionCheck the installed Venueless version by examining package.json, setup.py, requirements.txt, or the application's version endpoint if available.Affected if The installed version falls within any affected version range for this vulnerability
-
Confirm social login feature is enabledReview Venueless configuration files (such as config.yaml, config.json, or environment variables) to determine if any social login provider (e.g., OAuth2, OpenID Connect for services like Google, GitHub, or custom OAuth) is configured and active.Affected if Social login is enabled and configured in the Venueless instance
-
Inspect redirect URL handling in social login flowExamine the application's authentication callback handlers and redirect logic in the source code or by reviewing network traffic during a social login attempt. Look for how the 'next', 'redirect', or 'state' parameter is processed after authentication.Affected if The application accepts and follows redirect URLs without strict allowlist validation of the target domain
-
Check for domain allowlist configurationReview the Venueless configuration to identify whether a domain allowlist or whitelist exists for permitted redirect destinations, and verify if it properly restricts redirect targets to trusted domains only.Affected if No strict allowlist-based validation is configured, or the allowlist permits arbitrary external domains
A user is affected if Venueless with social login enabled is running and the redirect URL validation either does not exist or fails to restrict destinations to an explicit allowlist of trusted domains.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based validation for all redirect URLs in the social login flow, ensuring only registered internal or approved external domains are permitted; also implement the 'rel=noopener' attribute on any links that open new tabs.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12863 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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