CVE-2020-37076
SQL injection in Victor CMS 1.0 post.php allows data extraction.
Is CVE-2020-37076 being exploited?
Not confirmed. CVE-2020-37076 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2020-37076?
CVE-2020-37076 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2020-37076?
Not known from our data. No patch reference has been recorded for CVE-2020-37076, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2020-37076 affect?
CVE-2020-37076 affects Victor CMS v1.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2020-37076?
Apply parameterized queries and upgrade if fixed
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exfiltrate DB data via UNION/boolean/error/time-based SQLi in post.php.
Patch when possible
- affected1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.