Threats / Fuel CMS / CVE-2020-17463
CVE-2020-17463
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Fuel CMS vulnerability
Fuel CMS 1.4.7 contains a SQL injection vulnerability in the col parameter across multiple administrative endpoints, allowing unauthenticated attackers to execute arbitrary database queries.
Verdict
Today item — known-exploited.
SQL injection in Fuel CMS 1.4.7 enables direct database manipulation through unsanitized parameters. Attackers can extract sensitive data, modify records, or escalate privileges. Active exploitation in the wild increases risk despite moderate EPSS score.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10).
Probability (EPSS)
EPSS 0.90044 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Fuel CMS, Fuel CMS. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious col parameter value containing SQL metacharacters to bypass input validation on the /pages/items, /permissions/items, or /navigation/items endpoints.
Business
Attackers gain unauthorized read access to sensitive database records including user credentials, configuration data, and business-critical content stored in the CMS.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute UNION-based or time-based SQL injection payloads to extract authentication tokens, password hashes, or administrative account details from the database.
Business
Compromised credentials enable lateral movement and privilege escalation, potentially granting full administrative control over the CMS and hosted content.
3
Lateral reach — past segmentation narrative 3
Attacker
I use SQL injection to modify or delete database records, including user permissions, page content, or navigation structures.
Business
Data integrity is compromised, leading to website defacement, loss of business data, and erosion of customer trust in the platform's reliability.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05