How severe is CVE-2020-20299?

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

Is CVE-2020-20299 being actively exploited?

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

What products are affected by CVE-2020-20299?

CVE-2020-20299 affects Weiphp. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-20299?

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

When was CVE-2020-20299 published?

CVE-2020-20299 was published on 2020-12-18 and last updated on 2026-06-17.

CVE-2020-20299

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

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Weiphp
Published: 2020-12-18
Last modified: 2026-06-17

Description

WeiPHP 5.0 does not properly restrict access to pages, related to using POST.

Frequently asked questions

What is CVE-2020-20299?: WeiPHP 5.0 does not properly restrict access to pages, related to using POST.
How severe is CVE-2020-20299?: CVE-2020-20299 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-20299 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-20299?: CVE-2020-20299 affects Weiphp. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-20299?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-20299 published?: CVE-2020-20299 was published on 2020-12-18 and last updated on 2026-06-17.

References

https://github.com/Y4er/Y4er.com/blob/master/content/post/weiphp5-unauthorized.md

Affected products (1)

cpe:2.3:a:weiphp:weiphp:5.0:*:*:*:*:*:*:*

More vulnerabilities in Weiphp

CVE-2020-20300 — Critical (CVSS 9.8): SQL injection vulnerability in the wp_where function in WeiPHP 5.0.
CVE-2025-55849 — High (CVSS 8.4): WeiPHP v5.0 and before is vulnerable to SQL Injection via the SucaiController.class.php file and the cancelTemplatee
CVE-2025-34045 — High (CVSS 7.5): A path traversal vulnerability exists in WeiPHP 5.0, an open source WeChat public account platform development…

All CVEs affecting Weiphp →