Security Resilience

CVE-2023-51332

Phpjabbers Meeting Room Booking System 1.0

Public PoC
Published
20 February 2025
Modified
04 November 2025
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0042 35th percentile
Risk Priority 37 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-51332 is a medium-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Phpjabbers Meeting Room Booking System. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 35th percentile by exploit likelihood (below the median); 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 SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A lack of rate limiting in the 'Forgot Password' feature of PHPJabbers Meeting Room Booking System v1.0 allows attackers to send an excessive amount of email for a legitimate user, leading to a possible Denial of Service (DoS) via a…

more

large amount of generated e-mail messages.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-51338Same product: Phpjabbers Meeting Room Booking System
CVE-2023-51336Same product: Phpjabbers Meeting Room Booking System
CVE-2023-40764Same vendor: Phpjabbers
CVE-2023-33561Same vendor: Phpjabbers
CVE-2023-51303Same vendor: Phpjabbers
CVE-2023-51339Same vendor: Phpjabbers
CVE-2023-48840Same vendor: Phpjabbers
CVE-2023-51326Same vendor: Phpjabbers
CVE-2023-51306Same vendor: Phpjabbers
CVE-2023-48831Same vendor: Phpjabbers

Affected Assets

phpjabbers
meeting room booking system
1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

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

documenting procedures for secure operation, error handling, restart/recovery and resource management (including references to 8.13/8.18) is a governance and dependency control that does not itself stop exploitation of a resource-shutdown flaw; any prevention would require other controls (e.g. code changes or runtime enforcement) configured to act on it

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-404, a class-level weakness, and none of its children carries one either.

References