CVE-2020-29280 json
The Victor CMS v1.0 application is vulnerable to SQL injection via the 'search' parameter on the search.php page.
published 5y ago modified 4mo ago also EUVD-2020-21655
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
The Victor CMS v1.0 application is vulnerable to SQL injection via the 'search' parameter on the search.php page.
Is CVE-2020-29280 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.90% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/BigTiger2020/Victor-CMS-/blob/main/README.md
third-party-advisory
-
github.com
/VictorAlagwu/CMSsite/issues/13
third-party-advisory
-
exploit-db.com
/exploits/48734
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2020-29280
- NVD CVE-2020-29280
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.