Security readout for executives and security teams
Plain-English summary
FineCMS had a server-side request forgery issue before 2017-07-06. A vulnerable image-data endpoint could be abused through crafted requests involving non-image files and a modified Host header. Business urgency depends on whether legacy FineCMS is internet-facing or can reach sensitive internal services.
Executive priority
Treat this as a legacy exposure check rather than a confirmed emergency. Prioritize if FineCMS is still deployed, internet-facing, or hosted in a network with access to sensitive internal systems.
Technical view
CVE-2017-10973 describes SSRF in application/lib/ajax/get_image_data.php in FineCMS before 2017-07-06. The source bundle links GitHub pull requests but provides no CVSS, CWE, CPEs, or detailed fixed-version metadata beyond the date boundary.
Likely exposure
Exposure is most likely limited to organizations still running FineCMS code older than 2017-07-06, especially where the affected endpoint is reachable. The bundle does not identify packaged versions, CPEs, hosted services, or downstream forks.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked as CISA KEV. SSRF impact can vary widely depending on network placement and reachable internal resources, but no exploit maturity evidence is supplied here.
Researcher notes
The record is sparse: no CVSS vector, no CWE mapping, no CPEs, and no exploit-status evidence. Analysis should stay anchored to the endpoint, pre-2017-07-06 date boundary, SSRF class, and referenced GitHub pull requests.
Mitigation direction
- Inventory FineCMS deployments and determine whether code predates 2017-07-06.
- Upgrade to a post-2017-07-06 FineCMS revision or vendor-confirmed fixed code.
- Review GitHub pull requests 10 and 11 for project-specific remediation context.
- Restrict public access to the affected endpoint if legacy code cannot be promptly replaced.
- Check server egress controls to limit access to internal metadata or private services.
Validation and detection
- Confirm whether application/lib/ajax/get_image_data.php exists in deployed FineCMS code.
- Verify deployed FineCMS source includes changes from the referenced July 2017 pull requests.
- Review access logs for unusual requests to the affected AJAX image-data endpoint.
- Assess whether the web server can reach sensitive internal services from its network segment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
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 lookupCVE-2017-10973 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/andrzuk/FineCMS/pull/11CVE reference · x_refsource_CONFIRM
- https://github.com/andrzuk/FineCMS/pull/10CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
