Security Resilience

CVE-2024-12543

Published
21 April 2025
Modified
15 April 2026
CVSS Score v4 5.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/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.0034 25th percentile
Risk Priority 22 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-2024-12543 is a medium-severity Improper Enforcement of Behavioral Workflow (CWE-841) vulnerability in Opentext Content Management (inferred from references). Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

User Enumeration and Data Integrity in Barcode functionality in OpenText Content Management versions 24.3-25.1on Windows and Linux allows a malicous authenticated attacker to potentially alter barcode attributes.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-79083Shared CWE-841
CVE-2026-41259Shared CWE-841
CVE-2024-0410Shared CWE-841
CVE-2026-13222Shared CWE-841
CVE-2023-1383Shared CWE-841
CVE-2023-42939Shared CWE-841
CVE-2025-13459Shared CWE-841
CVE-2024-44128Shared CWE-841
CVE-2025-48481Shared CWE-841
CVE-2026-67279Shared CWE-841

Affected Assets

Opentext
Content Management
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement can require each successive workflow step to present the proper authorization context before proceeding.

Re-authentication requirements can be placed at critical workflow steps to ensure the actor has performed prior behaviors.

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

Secure development lifecycle requires explicit workflow enforcement in multi-step processes.

blocks

A.8.26 only requires that workflow-enforcement requirements be identified during requirements gathering; it performs no enforcement itself and leaves the weakness fully exploitable

blocks

A.8.27 mandates security-by-design principles (least privilege, default deny, fail securely, distrust external input, defense-in-depth, assume-breach, zero-trust verification) plus design reviews that can catch and block many workflow-sequence enforcement gaps before they ship, but leaves a bounded remainder (e.g. complex multi-step business-process flows whose required ordering is not captured by any listed principle or standard attack-pattern review).

prevents

Secure coding practices can prevent missing workflow checks but do not define the control itself.

finds

Security testing can detect workflow bypasses but does not enforce them at runtime.

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.

  • No fine-grained STIG row for CWE-841, a class-level weakness, and none of its children carries one either.

References