CVE-2023-6467
Thecosy Icecms 2.0.1
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2023-6467 is a low-severity Improper Enforcement of a Single, Unique Action (CWE-837) vulnerability in Thecosy Icecms. Its CVSS base score is 3.1 (Low).
Operationally, ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-58701
Vulnerability Data
A vulnerability was found in Thecosy IceCMS 2.0.1. It has been rated as problematic. This issue affects some unknown processing of the file /Websquare/likeClickComment/ of the component Comment Like Handler. The manipulation leads to improper enforcement of a single, unique…
more
action. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-246617 was assigned to this vulnerability.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.3V6.5.1V7.6.2V17.3.1
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.
Authorization policy enforcement can include rules that restrict actions to a single use.
Logical access controls can incorporate mechanisms that block replay or repeated actions.
Preventing execution of unauthorized or duplicate actions directly addresses single-use enforcement.
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.
Access-control rules can enforce single-use or uniqueness constraints, but the control is broader than this specific weakness.
Managing access rights can include rules that limit an action to one occurrence, yet the control addresses rights in general.
Secure SDLC practices can require design controls for single-use actions, but the control addresses the entire lifecycle.
Application-security requirements can specify single-action enforcement, yet the control is wider in scope.
Secure-coding standards can mandate checks that prevent repeated actions, but the control covers many coding issues.
Information-access-restriction mechanisms can implement single-action limits, but the control covers broader access-restriction needs.