CVE-2026-13207
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 · uneditedFUXA versions 1.3.1 and prior contain an authentication bypass vulnerability via dot-segment path normalization in the REST API. The API router fails to normalize dot-segment sequences before applying authentication middleware, allowing unauthenticated requests to access protected endpoints by prefixing paths with dot-segments such as /api/./users, /api/./roles, and /api/project/../users. These requests bypass authentication checks and return sensitive user and role data without credentials.
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 confidenceFUXA versions 1.3.1 and prior have an authentication bypass vulnerability in the REST API router. The API fails to normalize dot-segment sequences (like /./ and /../) before applying authentication middleware, allowing attackers to bypass authentication on protected endpoints by prefixing paths with dot-segments such as /api/./users or /api/project/../users, enabling unauthenticated access to sensitive user and role data.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installed FUXA versionCheck the package.json file in the FUXA installation directory, or run 'npm list fuxa' or check the about/page in the FUXA web interfaceAffected if The installed version is 1.3.1 or any version prior to 1.3.1
-
Verify API server is runningCheck if the FUXA server process is active and listening on its API port (usually 1881 or 3001)Affected if The API server is accessible and running
-
Test authentication bypass with dot-segment pathsSend HTTP requests to protected API endpoints using dot-segment prefixes, for example: GET /api/./users or GET /api/project/../users, and observe if authentication is bypassedAffected if The server returns user data, role data, or other sensitive information without requiring valid authentication credentials when dot-segments are used in the path
-
Compare against expected authentication behaviorAttempt the same API requests without dot-segments (e.g., GET /api/users) and verify they properly require authenticationAffected if Requests without dot-segments correctly require auth but dot-segment requests return data without auth, confirming the bypass exists
A FUXA installation is affected if it runs version 1.3.1 or prior AND the API server is accessible, with authentication being bypassed when dot-segment sequences are appended to protected API paths.
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 path normalization in the API routing layer to resolve dot-segment sequences (./ and ../) before authentication middleware executes. Ensure all API routes are processed through normalized paths and validate that authentication is consistently applied across all protected endpoints.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13207 — 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-13207 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