Cyber Resilience

CVE-2025-66384

Published
28 November 2025
Modified
15 April 2026
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L
EPSS Score 0.0035 28th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2025-66384 is a high-severity Incorrect Provision of Specified Functionality (CWE-684) vulnerability. Its CVSS base score is 8.2 (High).

Operationally, ranked at the 28th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

app/Controller/EventsController.php in MISP before 2.5.24 has invalid logic in checking for uploaded file validity, related to tmp_name.

CWE(s)
CWE-684

Related Threats

CVEs Like This One

CVE-2023-24845Shared CWE-684
CVE-2025-55174Shared CWE-684
CVE-2025-54568Shared CWE-684
CVE-2025-58325Shared CWE-684
CVE-2026-44597Shared CWE-684
CVE-2025-47227Shared CWE-684
CVE-2024-5005Shared CWE-684
CVE-2024-6502Shared CWE-684
CVE-2023-5158Shared CWE-684
CVE-2024-20317Shared CWE-684

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities are performed precisely to discover when delivered functionality fails to match published specifications.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and supporting tools reduces the chance that specified functionality will be implemented incorrectly.

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 enforce spec-compliant functionality and testing, while eliminating this weakness fulfills only part of the control's broader monitoring 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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance validates that implemented functionality conforms to specifications before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes requirements and verification activities that directly reduce the risk of delivering functionality that deviates from published specifications.

A.8.26 Application security requirements partial match
prevents

Explicit application security requirements and acceptance criteria help ensure the delivered software matches its intended specifications.

A.8.32 Change management partial match
prevents

Change management processes reduce the chance of unintended functional deviations during updates, though they do not directly address initial specification conformance.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

RHEL 9 (1 rule)
  • V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-684

References