Cyber Resilience

CVE-2023-1758

Phpmyfaq ≤ 3.1.12

Public PoC
Published
05 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0054 42th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2023-1758 is a medium-severity Special Element Injection (CWE-75) vulnerability in Phpmyfaq Phpmyfaq. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository thorsten/phpmyfaq prior to 3.1.12.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
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.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-62519Same product: Phpmyfaq Phpmyfaq
CVE-2025-68951Same product: Phpmyfaq Phpmyfaq
CVE-2023-0310Same product: Phpmyfaq Phpmyfaq
CVE-2023-5316Same product: Phpmyfaq Phpmyfaq
CVE-2023-0313Same product: Phpmyfaq Phpmyfaq
CVE-2023-1880Same product: Phpmyfaq Phpmyfaq
CVE-2023-2752Same product: Phpmyfaq Phpmyfaq
CVE-2023-2550Same product: Phpmyfaq Phpmyfaq
CVE-2026-34974Same product: Phpmyfaq Phpmyfaq
CVE-2023-5863Same product: Phpmyfaq Phpmyfaq

Affected Assets

phpmyfaq
phpmyfaq
≤ 3.1.12

Mitigating Controls

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 require input sanitization to block special-element injection.

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 catches injection vulnerabilities but does not itself implement the sanitization fix.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

prevents

Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.

prevents

Application security requirements explicitly call for controls against injection flaws including special-element handling.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.

prevents

Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.

References