How severe is CVE-2020-18439?

CVE-2020-18439 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2020-18439 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-18439?

CVE-2020-18439 affects Phpok. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-18439?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-18439 published?

CVE-2020-18439 was published on 2021-11-02 and last updated on 2026-06-17.

CVE-2020-18439

CVE-2020-18439 is a critical-severity vulnerability in Phpok with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v2: 6.4
EPSS exploit prediction: 1% (58th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phpok
Published: 2021-11-02
Last modified: 2026-06-17

Description

An issue was discoverered in in function edit_save_f in framework/admin/tpl_control.php in qinggan phpok 5.1, allows attackers to write arbitrary files or get a shell.

Frequently asked questions

What is CVE-2020-18439?: An issue was discoverered in in function edit_save_f in framework/admin/tpl_control.php in qinggan phpok 5.1, allows attackers to write arbitrary files or get a shell.
How severe is CVE-2020-18439?: CVE-2020-18439 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-18439 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-18439?: CVE-2020-18439 affects Phpok. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-18439?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-18439 published?: CVE-2020-18439 was published on 2021-11-02 and last updated on 2026-06-17.

References

https://github.com/qinggan/phpok/issues/4

Affected products (1)

cpe:2.3:a:phpok:phpok:5.1:*:*:*:*:*:*:*

More vulnerabilities in Phpok

CVE-2022-47129 — Critical (CVSS 9.8): PHPOK v6.3 was discovered to contain a remote code execution (RCE) vulnerability.
CVE-2022-40889 — Critical (CVSS 9.8): Phpok 6.1 has a deserialization vulnerability via framework/phpok_call.php.
CVE-2022-29363 — Critical (CVSS 9.8): Phpok v6.1 was discovered to contain a deserialization vulnerability via the update_f() function in login_control.php.…
CVE-2020-18440 — Critical (CVSS 9.8): Buffer overflow vulnerability in framework/init.php in qinggan phpok 5.1, allows attackers to execute arbitrary code.
CVE-2020-16629 — Critical (CVSS 9.8): PhpOK 5.4.137 contains a SQL injection vulnerability that can inject an attachment data through SQL, and then call the…
CVE-2018-12491 — Critical (CVSS 9.8): PHPOK 4.9.032 has an arbitrary file upload vulnerability in the import_f function in…

All CVEs affecting Phpok →