Security Resilience

CVE-2026-27161

Info Disclosure in Getsimple-Ce Getsimple Cms ≤ 3.3.22

Public PoCInfo Disclosure
Published
21 February 2026
Modified
24 February 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0052 43th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-27161 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Getsimple-Ce Getsimple Cms. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-27161 is a vulnerability in all versions of GetSimple CMS, a content management system. The issue arises because the software relies on .htaccess files to restrict access to sensitive directories such as /data/ and /backups/. When Apache's AllowOverride directive is disabled—a configuration common in hardened or shared hosting environments—these .htaccess protections are silently ignored, enabling unauthorized access to those directories.

Unauthenticated attackers can exploit this vulnerability remotely with low attack complexity, requiring no privileges or user interaction. Successful exploitation allows them to list directory contents and download sensitive files, including authorization.xml, which contains cryptographic salts and API keys. The CVSS v3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting high confidentiality impact and mapping to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor).

The GitHub Security Advisory at https://github.com/GetSimpleCMS-CE/GetSimpleCMS-CE/security/advisories/GHSA-f63g-xh6j-q56g, published on 2026-02-21, confirms that no fix is available at the time of disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GetSimple CMS is a content management system. All versions of GetSimple CMS rely on .htaccess files to restrict access to sensitive directories such as /data/ and /backups/. If Apache AllowOverride is disabled (common in hardened or shared hosting environments), these…

more

protections are silently ignored, allowing unauthenticated attackers to list and download sensitive files including authorization.xml, which contains cryptographic salts and API keys. This issue does not have a fix at the time of publication.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-27147Same product: Getsimple-Ce Getsimple Cms
CVE-2026-27202Same product: Getsimple-Ce Getsimple Cms
CVE-2026-27146Same product: Getsimple-Ce Getsimple Cms
CVE-2026-26351Same product: Getsimple-Ce Getsimple Cms
CVE-2024-55086Same product: Getsimple-Ce Getsimple Cms
CVE-2024-55088Same product: Getsimple-Ce Getsimple Cms
CVE-2025-48492Same product: Getsimple-Ce Getsimple Cms
CVE-2024-55085Same product: Getsimple-Ce Getsimple Cms
CVE-2026-28495Same product: Getsimple-Ce Getsimple Cms
CVE-2025-14726Shared CWE-200

Affected Assets

getsimple-ce
getsimple cms
≤ 3.3.22

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized actors from obtaining sensitive information.

Information flow enforcement structurally prevents sensitive data from reaching unauthorized recipients.

Protection of information at rest prevents unauthorized exposure of stored sensitive data.

Transmission confidentiality mechanisms stop exposure of sensitive data on the wire.

Least privilege reduces the set of actors who can reach sensitive information.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Suppressing system details, error specifics, and previous log-on information until successful authentication reduces the information an unauthenticated attacker can gather.

blocks

Requiring encryption, access controls, and recipient authentication for transfers directly reduces the chance that sensitive data reaches an unauthorized observer.

blocks

Secure delivery, protected storage, and confidentiality of allocation records limit exposure of authentication material to unauthorized observers.

blocks

A.8.1's policy+enforcement on access controls, storage encryption, malware protection, device registration, remote wipe/lock, physical/logical protections, partitioning, and BYOD separation (plus config enforcement via 8.9) stops most unauthorized exposure of sensitive data from endpoints; named remainder is exposures via error messages, side channels or non-endpoint vectors (see A.8.3 mostly on same CWE).

blocks

A.8.10 mandates timely, secure deletion (overwriting, crypto erase, certified disposal, automation per retention policy) of unneeded sensitive information on all media, which directly stops most exposure paths in CWE-200; the bounded remainder is exposure that is not a retention issue at all (e.g. CWE-209 error messages, CWE-203 observable discrepancies, CWE-215 debug code).

blocks

data masking (incl. pseudonymization/anonymization) directly limits exposure of sensitive data to unauthorized actors per the purpose and guidance, covering most but not all vectors in CWE-200 (e.g. residual indirect re-identification risks or non-masked exposure paths like error messages remain nameable)

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References