Cyber Resilience

CVE-2023-4654

Instantcms ≤ 2.16.1

Public PoC
Published
31 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 3.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2023-4654 is a low-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in Instantcms Instantcms. Its CVSS base score is 3.5 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Web Session Cookie (T1539); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository instantsoft/icms2 prior to 2.16.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4649Same product: Instantcms Instantcms
CVE-2023-4189Same product: Instantcms Instantcms
CVE-2023-4879Same product: Instantcms Instantcms
CVE-2024-50348Same product: Instantcms Instantcms
CVE-2023-4652Same product: Instantcms Instantcms
CVE-2023-4187Same product: Instantcms Instantcms
CVE-2023-4653Same product: Instantcms Instantcms
CVE-2023-4655Same product: Instantcms Instantcms
CVE-2025-59055Same product: Instantcms Instantcms
CVE-2023-4650Same product: Instantcms Instantcms

Affected Assets

instantcms
instantcms
≤ 2.16.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-614

Forces the Secure flag on session cookies, preventing their transmission over unauthenticated HTTP channels.

addresses: CWE-614

Enforcing confidentiality on transmitted sensitive cookies requires the Secure attribute, preventing exposure on insecure channels.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.DS-02 mostly match
prevents

Setting the Secure attribute is a direct mechanism for protecting sensitive session data in transit over HTTPS.

PR.PS-01 mostly match
prevents

Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require correct use of security attributes such as the cookie Secure flag.

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.

mitigates

Use of cryptography control mandates encryption in transit, which HTTPS provides, but does not specifically require the Secure cookie attribute.

prevents

Application security requirements can include cookie security settings, but the control is broader and does not explicitly mandate the Secure attribute.

prevents

Secure coding practices directly prevent missing the Secure attribute on sensitive cookies, though the control covers many other coding issues.

degrades

Secure authentication control requires protection of session credentials, directly addressed by setting the Secure flag on sensitive cookies.

References