CVE-2022-30007: GXCMS V1.5 has a file upload vulnerability in the background
CVE-2022-30007 is a high-severity flaw (CVSS 7.2) affecting gxcms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
GXCMS V1.5 has a file upload vulnerability in the background. The vulnerability is the template management page. You can edit any template content and then rename to PHP suffix file, after calling PHP file can control the server.
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.2 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | None |
| EPSS exploit chance | 1.0% (top 38%) |
| CISA exploited list | No |
| Weakness | CWE-434 |
| Published | 2022-05-17 |
| 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-2022-30007?
gxcms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-30007 being exploited?
CVE-2022-30007 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-2022-30007 affect?
CVE-2022-30007 affects gxcms. Severity is high (CVSS 7.2). GXCMS V1.5 has a file upload vulnerability in the background. The vulnerability is the template management page. You can edit any template content and then rename to PHP suffix file, after calling PHP file can control the server.
How urgent is CVE-2022-30007?
Priority 46/100. High severity; Public exploit reference