CVE-2008-4128
Cisco IOS Cross-Site Request Forgery Vulnerability
Multiple cross-site request forgery (CSRF) vulnerabilities in the HTTP Administration component in Cisco IOS 12.4 on the 871 Integrated Services Router allow remote attackers to execute arbitrary commands via (1) a certain "show privilege" command to the /level/15/exec/- URI, and (2) a certain "alias exec" command to the /level/15/exec/-/configure/http URI. NOTE: some of these details are obtained from third party information.
Published Updated Sources: NVD, Cisco (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, Exploit-DB
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Jul 13, 2026
EPSS
33%
ahead of 98% of scored CVEs
CVSS base
9.3
high · 2 sources
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade IOS to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Federal deadline Jul 16, 2026 — passed 38 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Cisco | IOS | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
Changed
Confidentiality
Changed
Integrity
Changed
Attack Complexity
M
Attack Vector
Network
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | medium | 2.8 | 1.4 | CNA, GHSA |
| 9.3 | CVSS 2.0 | high | 8.6 | 10 | NVD |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Weakness & attack patterns
- CWE-352
Inferred from the weakness class — not observed against this CVE.
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Jul 13, 2026
Federal deadline
Jul 16, 2026
passed 38 days ago
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
8
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /level/15/exec/-, /level/15/exec/-/configure/http.
- Prioritize edge telemetry for network-reachable IOS.
- Monitor for scanner or exploit-pattern traffic after 9 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 9.3 (AV:N)
Jul 14, 2026 · NVD
Added to CISA KEV catalog
Jul 13, 2026 · CISA
- 2022
Added · GHSA-6977-wjv6-r929 published (high)
May 2, 2022 · GitHub Security Advisory
- 2008
Initial · CVE published
Sep 18, 2008 · NVD
Added · Verified remote entry: Cisco Router - HTTP Administration Cross-Site Request Forgery / Command Execution (1)
Sep 17, 2008 · Exploit-DB
References
12 on the record
- jbrownsec.blogspot.com/2008/09/cisco-0day-released.html
Broken Link
- www.securityfocus.com/bid/31218
Broken Link, Exploit, Third Party Advisory, VDB Entry
- exchange.xforce.ibmcloud.com/vulnerabilities/45226
Third Party Advisory, VDB Entry
- www.exploit-db.com/exploits/6476
Exploit, Third Party Advisory, VDB Entry
- www.exploit-db.com/exploits/6477
Exploit, Third Party Advisory, VDB Entry
- media.defense.gov/2026/Jul/09/2003959498/-1/-1/1/CSA_IMPROVE_ROUTER_HYGIENE.PDF
Third Party Advisory, US Government Resource
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2008-4128
US Government Resource
- www.cisco.com/c/en/us/obsolete/ios-nx-os-software/cisco-ios-software-releases-12-4-mainline.html
Product, Vendor Advisory
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2008-4128 is Cisco IOS Cross-Site Request Forgery Vulnerability, a high vulnerability affecting IOS from Cisco. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 9 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.3 describes technical severity, while EPSS 33% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.