LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20106: Lithium Forum Compose Message server-side request forgery

A vulnerability, which was classified as critical, has been found in Lithium Forum 2017 Q1. This issue affects some unknown processing of the component Compose Message Handler. The manipulation of the argument upload_url leads to server-side request forgery. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-20106 is a server-side request forgery issue in Lithium Forum 2017 Q1. A low-privileged local attacker could manipulate the message composition upload URL so the server makes unintended requests. The sources describe public exploit disclosure, but do not show confirmed active exploitation.

Executive priority

Treat this as a targeted legacy-platform risk. Prioritize if Lithium Forum 2017 Q1 is still in use, especially in environments with internal network reachability from the forum server.

Technical view

The issue is mapped to CWE-918 and affects the Compose Message Handler, specifically handling of the upload_url argument. CVSS 3.1 scores it 5.3 with local attack vector, low complexity, low privileges, no user interaction, and limited confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Lithium Forum 2017 Q1 deployments. The provided vector indicates local access and low privileges are required, so externally exposed forums are not necessarily exploitable without that access path.

Exploitation context

The CVE record says an exploit has been publicly disclosed and may be used. CISA KEV is false in the bundle, and no cited source in the bundle confirms active exploitation in the wild.

Researcher notes

The public bundle lacks vendor patch details, affected CPEs, and precise handler internals. The local attack vector and low privilege requirement materially reduce broad internet-scale risk, but SSRF can matter when the forum server has privileged internal network access.

Mitigation direction

  • Inventory Lithium Forum instances and confirm whether any run 2017 Q1.
  • Check official vendor or platform support guidance for a fixed release or supported migration path.
  • Restrict access to message-composition and upload functions to trusted users and networks where feasible.
  • Monitor server egress and internal request logs for unexpected forum-originated requests.
  • Retire or isolate unsupported 2017-era forum deployments if no vendor fix is available.

Validation and detection

  • Confirm product name, build, and deployment date against Lithium Forum 2017 Q1.
  • Review whether the Compose Message Handler and upload capability are enabled.
  • Check access controls for users who can reach message composition functionality.
  • Inspect logs for unusual server-side requests initiated through forum upload workflows.
  • Document findings without running exploit payloads or offensive SSRF tests.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-20106 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L1.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2017-20106Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LithiumForum2017 Q1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.