CVE-2020-36537: A vulnerability was found in Everywhere CMS
CVE-2020-36537 is a medium-severity flaw (CVSS 6.3) affecting everywhere cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A vulnerability was found in Everywhere CMS. It has been classified as critical. Affected is an unknown function. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.7% (top 48%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2022-06-07 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-36537?
everywhere cms: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-36537 being exploited?
CVE-2020-36537 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-36537 affect?
CVE-2020-36537 affects everywhere cms. Severity is medium (CVSS 6.3). A vulnerability was found in Everywhere CMS. It has been classified as critical. Affected is an unknown function. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely.
How urgent is CVE-2020-36537?
Priority 35/100. No elevated risk signals yet.