Security readout for executives and security teams
Plain-English summary
CVE-2018-12491 describes an arbitrary file upload issue in PHPOK 4.9.032. The public description says a PHP file can be uploaded inside a PHP-named ZIP archive through the import function. Source data lacks CVSS, CPEs, and vendor fix details, so urgency depends on whether PHPOK 4.9.032 is deployed and reachable.
Executive priority
Treat as a targeted validation item rather than a confirmed emergency. If PHPOK 4.9.032 is present and admin import is reachable, prioritize remediation because arbitrary file upload can create serious compromise paths.
Technical view
The reported flaw is in import_f in framework/admin/modulec_control.php. The described bypass involves accepting a .php file inside a .php.zip archive, similar to CVE-2018-8944. The bundle does not state authentication requirements, execution path, fixed versions, or formal CWE/CVSS scoring.
Likely exposure
Organizations are likely exposed only if they run PHPOK 4.9.032. Exposure is higher where administrative import functionality is reachable by untrusted users or weakly protected accounts. The source bundle does not provide CPEs or complete affected product metadata.
Exploitation context
The CVE description includes a public proof concept at the behavior level, but the bundle provides no exploit code details here. CISA KEV is false, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is limited to the CVE record description and a public audit reference. Key unknowns include authentication context, upload storage location, server-side execution conditions, and fixed release information. Avoid assuming active exploitation without additional sourced evidence.
Mitigation direction
- Identify any PHPOK deployments and confirm exact version 4.9.032 exposure.
- Restrict access to administrative import functionality to trusted administrators only.
- Review vendor or project guidance for fixed versions or official mitigations.
- Disable or monitor archive-based imports if they are not business-critical.
Validation and detection
- Inventory web applications for PHPOK and confirm installed versions.
- Check whether framework/admin/modulec_control.php import functionality is reachable.
- Review upload handling controls for archive contents and PHP file types.
- Inspect web roots and upload directories for unexpected PHP files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-12491 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/SukaraLin/php_code_audit_project/blob/master/phpok/Phpok%204.9.032%E4%BB%A3%E7%A0%81%E5%AE%A1%E8%AE%A1.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.