CVE-2016-3691
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 · uneditedRoutes in Kallithea before 0.3.2 allows remote attackers to bypass the CSRF protection by using the GET HTTP request method.
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 confidenceKallithea versions before 0.3.2 had a CSRF protection bypass vulnerability where state-changing operations could be performed via GET requests instead of requiring POST. This allowed attackers to craft malicious links that could perform unauthorized actions (like modifying repositories or user settings) without needing a valid CSRF token, since GET requests were not properly protected against CSRF.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.3.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Kallithea versionCheck the installed Kallithea version by reviewing the version file, package metadata, or running a version command if available in the Kallithea instanceAffected if The installed version is 0.3.1 or any version before 0.3.2 (e.g., 0.3.0, 0.3, 0.2.x, etc.)
-
Verify state-changing operations accept GET requestsTest whether GET requests to state-changing endpoints (such as repository creation, user modification, or settings changes) are processed without returning a method-not-allowed errorAffected if GET requests successfully trigger state-changing actions instead of being rejected as improper HTTP method
-
Confirm CSRF token enforcement on POST requestsSubmit a POST request to a state-changing endpoint without a valid CSRF token and observe whether the request is rejectedAffected if POST requests without CSRF tokens are accepted and the action is performed, indicating missing CSRF validation
-
Inspect application CSRF configurationReview the Kallithea application configuration or source code for CSRF middleware/settings and check if GET requests are explicitly excluded from CSRF protectionAffected if CSRF protection is configured to allow GET requests for state-changing operations or CSRF middleware is missing entirely
A defender is affected if their Kallithea installation is version 0.3.1 or earlier and GET requests can perform state-changing operations without CSRF token validation.
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 dataUpgrade to Kallithea 0.3.2 or later, which enforces POST-only requests for state-changing operations and properly validates CSRF tokens.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3691 — 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-2016-3691 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