Questions For ConfluenceApplication · Atlassian
CVE-2018-13393
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 · uneditedThe convertCommentToAnswer resource in Atlassian Confluence Questions before version 2.6.6, the bundled version of Confluence Questions was updated to a fixed version in Confluence version 6.9.0, allows remote attackers to modify a comment into an answer via a Cross-site request forgery (CSRF) vulnerability.
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 confidenceThis is a CSRF (Cross-site request forgery) vulnerability in the convertCommentToAnswer resource of Atlassian Confluence Questions plugin. An attacker can trick an authenticated Confluence user into unknowingly submitting a request that converts a comment into an answer, allowing unauthorized manipulation of Q&A content.
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
Questions For ConfluenceApplication
< 2.6.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 if Atlassian Questions plugin is installedNavigate to Confluence Administration > Manage add-ons or look for the Questions app in the Confluence header. Alternatively, check the installed plugins via the REST API endpoint /rest/plugins/1.0/Affected if The Atlassian Questions For Confluence plugin is present in the Confluence instance
-
Check the installed version of Atlassian QuestionsIn Manage add-ons, locate Atlassian Questions For Confluence and read the version number from the plugin details. Or query: GET /rest/plugins/1.0/installedAffected if The plugin version is lower than 2.6.6 (e.g., 2.5.0, 2.4.0, etc.)
-
Verify the convertCommentToAnswer endpoint existsCheck if the endpoint /questions/api/v1/comments/{commentId}/convertToAnswer is accessible. This can be confirmed by examining the plugin's REST API definitions or testing with an authenticated session using a tool like curlAffected if The endpoint responds to authenticated requests without requiring a CSRF token in the request header
-
Confirm lack of CSRF token validation on state-changing endpointsSubmit a POST request to the convertCommentToAnswer endpoint using a session cookie but without the X-Atlassian-Token: no-check header or any CSRF token. Observe if the request succeedsAffected if Requests succeed without CSRF token validation, meaning the vulnerable endpoint lacks anti-CSRF protection
A Confluence instance with Atlassian Questions For Confluence plugin versions below 2.6.6 installed is affected if the convertCommentToAnswer REST endpoint is accessible 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 data2.6.6
Upgrade to Confluence Questions version 2.6.6 or later (or Confluence 6.9.0+), and implement anti-CSRF tokens on state-changing endpoints.
Fix this in Questions For Confluence
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13393 — 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-2018-13393 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