Skip to content
Fencer Intel
critical 9.8

CVE-2020-17463 kev in the critical feed json

FUEL CMS 1.4.7 allows SQL Injection via the col parameter to /pages/items, /permissions/items, or /navigation/items.

published 6y ago modified 4mo ago also EUVD-2020-9415

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2021-12-10
epss
89.7%
EPSS 89.7% chance of exploitation in 30 days, percentile 99.7%
public exploits
0
none known, plus a Nuclei check

Summary

FUEL CMS 1.4.7 allows SQL Injection via the col parameter to /pages/items, /permissions/items, or /navigation/items.

Patch / fix

cisa required action Apply updates per vendor instructions.

Is CVE-2020-17463 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 Fencer

Timeline

  1. Published
  2. Added to CISA KEV
  3. CISA patch deadline
  4. CISA SSVC: exploitation active

Known exploited

Added
4y ago
Patch by
2022-06-10 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Fuel CMS, Fuel CMS
CISA name
Fuel CMS SQL Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

89.69% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Fuel CMS 1.4.7 - SQL Injection nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/158840/Fuel-CMS-1.4.7-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 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

Sources

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.