Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to admin update handler
-
DeliverySubmit form with internal/metadata URL
-
ExploitServer fetches URL via file_get_contents (SSRF)
-
ExecutionResponse written to /Tmpfile.zip
-
PersistDownload web-accessible Tmpfile.zip
-
ImpactExfiltrate cloud metadata credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with access to the GetSimple CMS CE update handler form (CVSS PR:H indicates high/administrative privileges), and the installed version must be prior to 1.5. The specific vulnerable mechanism: the update handler passes a user-supplied URL to file_get_contents() after only FILTER_VALIDATE_URL format validation with no destination/scheme/IP allowlisting, and the fetched body is written to the web-accessible path /Tmpfile.zip and left in place even when it is not a valid ZIP. LIMITING FACTORS that reduce real-world risk: it is NOT unauthenticated (admin-level form access is needed), so it is primarily an insider or post-credential-compromise vector; full read-back depends on the server being able to reach the targeted internal/metadata endpoint (e.g. 169.254.169.254 only yields credentials in cloud environments that expose an unauthenticated metadata service). No special non-default configuration is otherwise required. |
| Impact | This is a full-read Server-Side Request Forgery (CWE-918) in GetSimple CMS CE's update handler, and the signals are moderately - not critically - alarming. The provided CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:L, base 7.5) reflects network-reachable, low-complexity exploitation, but critically requires PR:H - high privileges, i.e. an authenticated administrator who can reach the update form. This authentication barrier substantially lowers real-world mass-exploitation risk. CISA's SSVC framing aligns: Exploitation=poc (not active), Automatable=no, Technical Impact=partial. No CISA KEV listing and no EPSS score were provided, so there is no evidence of active or widespread exploitation. The signals are therefore internally consistent and point to a genuine but bounded issue: a privileged insider or an attacker who has already compromised an admin session can pivot to internal services and cloud metadata (169.254.169.254) to harvest credentials, but this is not a drive-by, unauthenticated internet-wide threat. One point to verify: the input vector carries UI:R, yet the described action (the authenticated user submitting the update form themselves) does not obviously require separate victim interaction - this UI:R may be conservative or an artifact; confirm with the vendor advisory. Overall priority: medium - elevate only for internet-exposed GetSimple CE instances where admin credentials or sessions may be weakly protected. |
| Exploit ScenarioDerived | An authenticated administrator (or an attacker who has hijacked an admin session) submits the update handler form with a URL pointing at an internal-only service or the cloud metadata endpoint (http://169.254.169.254/...). The server fetches that URL via file_get_contents() after only FILTER_VALIDATE_URL format checks, writes the response body to the web-accessible /Tmpfile.zip, and - because the file is not deleted when the content is not a valid ZIP - the attacker simply downloads /Tmpfile.zip to read the internal response, exfiltrating metadata credentials or internal service data. Publicly available exploit code exists (SSVC Exploitation=poc). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Full-read server-side request forgery in GetSimple CMS CE versions prior to 1.5 allows an authenticated attacker with access to the update handler form to make the server fetch arbitrary URLs and read the response body back from a web-accessible file. The handler applies only FILTER_VALIDATE_URL format checking with no destination or scheme allowlisting, so requests can be aimed at internal-only services and cloud metadata endpoints such as 169.254.169.254, with the fetched body written to /Tmpfile.zip and left in place even when it is not a valid ZIP. Exploitation requires high privileges (CVSS PR:H) and the installed version must be below 1.5; publicly available exploit code exists, but there is no confirmed active exploitation (CISA KEV), and vendor-released patch 1.5 is available.
RemediationAI
Upgrade GetSimple CMS CE to version 1.5, the vendor-released patch that fixes CVE-2026-56661, following the advisory at https://github.com/GetSimpleCMS-CE/GetSimpleCMS-CE/security/advisories/GHSA-r7v8-mx29-5q8h; this is the only complete fix and should be prioritized on any instance below 1.5. Where patching must be delayed, apply compensating controls that directly target the two exploitation prerequisites - administrative form access and outbound reachability - for example restricting access to the CMS administrative interface to trusted management networks or placing it behind an authenticated reverse proxy, which reduces exposure to insiders and post-compromise attackers but does not eliminate risk if an admin account is already compromised. Additionally, egress-filter the web server so it cannot reach link-local (169.254.0.0/16) and internal RFC1918 ranges, and where the host is in a cloud environment enforce IMDSv2 token-required metadata access or block the metadata endpoint; note that strict egress filtering can break legitimate update/download functionality the CMS expects to perform over the internet. Because the fetched response is written to the web-accessible path /Tmpfile.zip and left behind when it is not a valid ZIP, also deny web access to that path at the web server or remove it on a schedule - this limits read-back but does not stop the server from issuing the internal request itself. Be aware that an authenticated account with update-handler privileges is required (CVSS PR:H), so credential hygiene and privileged-account monitoring remain relevant, and note that public exploit code exists for this flaw even though no confirmed in-the-wild exploitation (CISA KEV) has been recorded.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic CWE-918 server-side request forgery rooted in PHP's file_get_contents() being called on a user-supplied URL. The code validates the input with FILTER_VALIDATE_URL, which only checks that the string is syntactically a URL - it does not restrict the host, IP range, or scheme, so loopback, RFC1918, link-local (169.254.0.0/16, including the 169.254.169.254 cloud metadata service), and other internal destinations are all reachable from the web server. The design choice to persist the response body to a web-accessible path (/Tmpfile.zip) and to leave that file in place when the content is not a valid ZIP converts what would normally be a blind SSRF into a full-read SSRF, since the attacker can simply request the written file to retrieve the internal response. The CVSS scope change (S:C) reflects that the vulnerable component can be used to affect resources beyond its own security authority - internal services and metadata credentials - while C:H captures the confidentiality impact of full response read-back. The affected package is tracked as cpe:2.3:a:getsimplecms-ce:getsimplecms-ce (all releases before 1.5) in the community edition of GetSimple CMS; the issue is catalogued as EUVD-2026-91017 in the ENISA EUVD database.
Know when Getsimplecms Ce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:L
Network-reachable but needs admin access to the update form (PR:H); no separate victim interaction (UI:N); scope changes as it reaches internal systems (S:C); impact is confidentiality-only read-back, so I:N/A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
GetSimple CMS is a content management system (CMS), and GetSimple CMS CE is the community edition of that CMS. Prior to version 1.5, the update handler fetches a user-supplied URL with file_get_contents() after only format validation (FILTER_VALIDATE_URL) - there is no validation of the request destination. An attacker who can submit the form can make the server issue requests to arbitrary destinations, including internal-only services and cloud metadata endpoints (169.254.169.254). The fetched response body is written to a web-accessible file (/Tmpfile.zip) and is not deleted when the content is not a valid ZIP, turning this into a full-read SSRF: the attacker can retrieve the response of the internal request directly. This issue has been patched in version 1.5.
Technical POC Analysis
CWE-918 (Server-Side Request Forgery).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
GetSimple CMS Community Edition deployments running versions below 1.5 are exposed to a server-side request forgery flaw that lets a privileged logged-in user direct the web server to retrieve internal resources - including cloud metadata services - and read the responses back through a web-accessible file. Because the retrieved content can include cloud instance credentials and internal-only service responses, a single trusted administrator account or a compromised admin session could become a pivot point into the wider cloud environment. Patch 1.5 is available, so remediation is straightforward, but any installation left unpatched should be treated as an active data-exposure risk until upgraded.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
More in Getsimplecms Ce
View allUnauthenticated administrator account creation affects GetSimple CMS (v3.4.0a and earlier) and its community edition Get
Remote code execution in GetSimple CMS CE (Community Edition) prior to 1.5 stems from a cross-site request forgery flaw
Administrator account takeover in GetSimple CMS CE 3.3.22 is achievable because the password reset endpoint is reachable
Remote code execution in GetSimple CMS CE prior to 1.5 allows an attacker to plant and execute PHP code as the web-serve
Stored cross-site scripting in GetSimple CMS CE 3.3.22 and earlier lets an authenticated user with page-editing rights p
Stored cross-site scripting in GetSimple CMS CE 3.3.22 and earlier allows an authenticated attacker to inject persistent
Stored local file inclusion in GetSimple CMS CE 3.3.22 and earlier lets any authenticated account holding page-editing r
EUVD-2026-91017
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB