Cyber Resilience

CVE-2023-45855

Path Traversal in Qdpm 9.2

Public PoCPath Traversal
Published
14 October 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.033 88th percentile
Risk Priority 83 floored blend · peak EPSS

Summary

CVE-2023-45855 is a high-severity Path Traversal (CWE-22) vulnerability in Qdpm Qdpm. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 12% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

qdPM version 9.2 contains a directory traversal vulnerability tracked as CVE-2023-45855 that permits unauthenticated listing of files and directories when an attacker navigates directly to the /uploads URI. The flaw is rated 7.5 under CVSS 3.1 and is classified under CWE-22 path traversal, affecting the confidentiality of any data stored under the web-accessible uploads path.

An attacker with network access and no credentials can exploit the issue to enumerate sensitive files and directory structures on the server. Because the attack requires no user interaction and succeeds over the network with low complexity, it enables broad reconnaissance that may expose configuration files, uploaded documents, or other restricted content.

Public references consist of a technical report on GitHub and the vendor site qdpm.net, yet neither source details an official patch or mitigation steps. The associated EPSS score has remained at 0.7930 without a material rise from a lower baseline, indicating no evident surge in exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

qdPM 9.2 allows Directory Traversal to list files and directories by navigating to the /uploads URI.

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-2020-7246Same product: Qdpm Qdpm
CVE-2025-21048Shared CWE-22
CVE-2026-23939Shared CWE-22
CVE-2024-7145Shared CWE-22
CVE-2023-42225Shared CWE-22
CVE-2024-33109Shared CWE-22
CVE-2023-35016Shared CWE-22
CVE-2025-10723Shared CWE-22
CVE-2023-1163Shared CWE-22
CVE-2024-43996Shared CWE-22

Affected Assets

qdpm
qdpm
9.2

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)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

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-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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 in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References