CVE-2023-5604
Published: 27 November 2023
Summary
CVE-2023-5604 is a critical-severity Code Injection (CWE-94) vulnerability in Asgaros Asgaros Forum. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 8.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
The Asgaros Forum WordPress plugin before version 2.7.1 is affected by a configuration weakness that permits forum administrators, who lack full WordPress super-administrator privileges, to enable uploads of dangerous file types such as .php and .phtml. This stems from improper handling of allowed file extensions and is tracked under CWE-94 and CWE-434, resulting in a CVSS 3.1 score of 9.8.
Forum administrators can exploit the flaw by altering plugin settings to permit these uploads, after which any unauthenticated remote attacker can upload and execute arbitrary code on the server without authentication or user interaction.
Public references point to WPScan advisories that document the issue in the affected plugin versions and indicate that the vulnerability is resolved in the 2.7.1 release.
The associated EPSS score remains at 0.0699 with no material increase observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57897
Vulnerability details
The Asgaros Forum WordPress plugin before 2.7.1 allows forum administrators, who may not be WordPress (super-)administrators, to set insecure configuration that allows unauthenticated users to upload dangerous files (e.g. .php, .phtml), potentially leading to remote code execution.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
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.
Dangerous file uploads can be detonated in the chamber to determine malice before any production write or execution occurs.
Requiring identifiable owners for portable devices reduces the attack surface for unrestricted uploads of dangerous file types via anonymous media.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Prevents unrestricted writing of arbitrary or malicious firmware by keeping hardware write-protect enabled except under tightly controlled manual procedures.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.
Scans files from external sources on download/open/execute, blocking unrestricted uploads of dangerous file types.