Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-53952 – Unauthenticated Admin Account Creation – GetSimple CMS ≤3.4.0a / GetSimpleCMS-CE ≤3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-53952 is a critical improper authorization vulnerability in GetSimple CMS and its community fork GetSimpleCMS-CE that allows a completely unauthenticated attacker to create a new administrator account. The flaw resides in the installation setup script, which the application fails to remove after initial setup due to a logic error in its own deletion routine, leaving it reachable and exploitable indefinitely. The issue carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: after installation, GetSimple CMS is supposed to self-delete admin/setup.php as a safeguard. The deletion logic contains a self-exclusion check that skips deletion whenever setup.php itself is the script being executed, so the file is never actually removed.
  • setup.php additionally performs no authentication or configuration-state check before processing POST requests, so it will still process account-creation submissions after the site has already been set up.
  • Attack vector: a remote, unauthenticated attacker sends a crafted POST request directly to /admin/setup.php on an internet-exposed instance.
  • Impact: the attacker can create a new administrator account, gaining full administrative access to the CMS. This can lead to complete loss of confidentiality, integrity, and availability of the site, including content tampering, malware/webshell deployment, and full site takeover.

Affected software

  • GetSimple CMS: versions 3.4.0a and earlier
  • GetSimpleCMS-CE: versions 3.3.22 and earlier

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: as of publication, no patched version has been released by either the GetSimple CMS or GetSimpleCMS-CE projects. Monitor vendor/project channels for an official fix and apply it as soon as it becomes available.
  • If no patch is available:
    • Manually delete or rename admin/setup.php (and any equivalent setup script) from the web root after installation, and verify it is not restored during updates.
    • Block external access to /admin/setup.php at the web server or WAF/reverse proxy layer.
    • Restrict access to the /admin/ directory to trusted IP ranges or place it behind additional authentication (e.g., HTTP basic auth, VPN).
    • Audit existing administrator accounts for any unauthorized/unrecognized entries and rotate credentials if compromise is suspected.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge