Security Resilience

CVE-2023-4560

Omeka S ≤ 4.0.4

Public PoC
Published
28 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0072 53th percentile
Risk Priority 51 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-2023-4560 is a medium-severity Improper Authorization of Index Containing Sensitive Information (CWE-612) vulnerability in Omeka Omeka S. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Improper Authorization of Index Containing Sensitive Information in GitHub repository omeka/omeka-s prior to 4.0.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4158Same product: Omeka Omeka S
CVE-2023-4561Same product: Omeka Omeka S
CVE-2023-4159Same product: Omeka Omeka S
CVE-2023-4157Same product: Omeka Omeka S
CVE-2024-49071Shared CWE-612
CVE-2025-3653Shared CWE-612
CVE-2024-25635Shared CWE-612
CVE-2019-25605Shared CWE-612
CVE-2025-3660Shared CWE-612
CVE-2025-3654Shared CWE-612

Affected Assets

omeka
omeka s
≤ 4.0.4

Mitigating Controls

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.AA-05 partial match
blocks

Directly enforces authorization policy and least privilege for access to sensitive data including indexes.

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

A.5.12 only defines and communicates a classification scheme (with owners accountable for applying it); it does not itself authorize, enforce, or restrict index access, so the improper authorization weakness and its exploitability remain untouched per the owner's labeling-dependency rule

blocks

A.5.15 only requires defining a topic-specific access control policy and determining requirements; it does not itself enforce, implement, or act on those rules to stop exploitation of an improperly authorized search index (per the owner's labeling rule and its positive form: policy/requirements are a dependency for other controls like A.8.3, not a preventer themselves).

blocks

A.5.18's provisioning, review, revocation and authorization steps (incl. owner approval, segregation, timely removal on role/employment change) directly enforce that only authorized actors can access the sensitive index, stopping exploitation in most cases; the bounded remainder is flawed index designs that leak outside any access control decision (e.g. via side-channel or mis-indexed public metadata).

blocks

Privileged access rights may be used to enforce index restrictions but are not the primary control.

blocks

A.8.3 directly restricts index access via configuration mechanisms, per-user/group rights, isolation, dynamic techniques, authentication and encryption, preventing exploitation for the dominant authorization slice of CWE-612; the bounded remainder is flawed index-generation logic itself (e.g. over-inclusion of sensitive docs before any access control is applied).

References