Skip to main content
← Vulnerabilities

CGI versions before 5.00 for Perl allow Content-Disposition parameter injection via unescaped double quotes in the header attachment…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 5.00
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.00.

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

CVE-2026-120647 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects CGI; fixed in 5.00.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Fix
Fixed in 5.00
None on Exploit-DB, Metasploit or GitHub

Summary

The CGI module for Perl (versions before 5.00) is affected. An attacker who can influence the filename passed to the attachment header can inject extra parameters into the Content-Disposition header, which may change the filename a user's browser saves the response under.

Read the original description

CGI versions before 5.00 for Perl allow Content-Disposition parameter injection via unescaped double quotes in the header attachment filename. header(-attachment => $name) writes $name into the quoted filename parameter of Content-Disposition without escaping double quotes. An application that passes request data as the attachment name can be made to send a second filename parameter, changing the name the response is saved under.

What to do

  • Upgrade to a fixed version: 5.00.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • CGI

    fixed in 5.00

Evidence 3

  1. Patch
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120647

Is CVE-2026-120647 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120647?

CGI: before 5.00.Source: cve.now feed data

How do I fix CVE-2026-120647?

Upgrade to a fixed version: 5.00.Source: cve.now feed data