Cyber Resilience

CVE-2024-3376

Oretnom23 Computer Laboratory Management System 1.0

Public PoC
Published
06 April 2024
Modified
17 June 2026
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.013 69th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2024-3376 is a high-severity EAR (CWE-698) vulnerability in Oretnom23 Computer Laboratory Management System. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 31% of CVEs by exploit likelihood; 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 SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability classified as critical has been found in SourceCodester Computer Laboratory Management System 1.0. This affects an unknown part of the file config.php. The manipulation of the argument url leads to execution after redirect. It is possible to initiate…

more

the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-259497 was assigned to this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8348Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-3131Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-3251Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-34480Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-31546Same product: Oretnom23 Computer Laboratory Management System
CVE-2025-45956Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-31545Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-3314Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-40443Same product: Oretnom23 Computer Laboratory Management System
CVE-2024-3316Same product: Oretnom23 Computer Laboratory Management System

Affected Assets

oretnom23
computer laboratory management system
1.0

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)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover execution paths that continue after a redirect.

Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.

Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

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.PS-06 mostly match
prevents

Secure SDLC practices directly prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.

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.

finds

Security testing can detect EAR flaws before deployment.

prevents

Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.

prevents

Application security requirements can mandate safe redirect patterns and post-redirect termination.

prevents

Secure architecture principles discourage continued execution after redirects.

prevents

Secure coding standards directly address proper redirect handling and flow termination.

prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References