CVE-2020-24898
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 Table Filter and Charts for Confluence Server app before 5.3.26 (for Atlassian Confluence) allows SSRF via the "Table from CSV" macro (URL parameter).
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 confidenceThe Table Filter and Charts for Confluence Server app before version 5.3.26 contains a Server-Side Request Forgery (SSRF) vulnerability in the 'Table from CSV' macro. The macro accepts a URL parameter to import CSV data without proper validation, allowing attackers to induce the server to make arbitrary requests to internal resources or external systems.
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< 5.3.26CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 version of Table Filter and ChartsNavigate to Confluence Administration > Manage apps > Table Filter and Charts for Confluence. Check the version number displayed in the app details.Affected if The version shown is less than 5.3.26 (e.g., 5.3.25, 5.3.0, etc.)
-
Verify Table from CSV macro is accessibleIn Confluence, attempt to create or edit a page and check if the 'Table from CSV' macro is available in the macro browser. Look for it under the Table Filter category or search for 'CSV'.Affected if The macro is listed and available for use in page editor
-
Review recent Confluence access logs for suspicious URL patternsExamine Confluence access logs (atlasian-confluence-access.log) for requests containing URL parameters that point to internal IP addresses (e.g., 127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual external domains.Affected if Logs show requests from the Table from CSV macro to internal resources or unexpected external URLs
-
Check for unexpected outbound connectionsReview Confluence server network connections or firewall logs for outbound HTTP/HTTPS requests originating from the Confluence application, particularly to internal services or non-standard ports.Affected if The Confluence server has made outbound requests to internal network resources that were not initiated by legitimate user actions
A user is affected if their Table Filter and Charts for Confluence app version is below 5.3.26 AND the Table from CSV macro is accessible and being used.
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 data5.3.26
Upgrade the Table Filter and Charts for Confluence app to version 5.3.26 or later. If immediate upgrading is not feasible, restrict network access to the Confluence instance and consider temporarily disabling the Table from CSV macro.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24898 — 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-2020-24898 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