CVE-2008-1968

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 1%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Multiple SQL injection vulnerabilities in Cezanne 7 allow remote authenticated users to execute arbitrary SQL commands via the FUNID parameter to (1) CFLookup.asp and (2) CznCommon/CznCustomContainer.asp.

CVSS v3
EG Score
0.0(none)
EPSS
53.3%
KEV
Not listed

Published

April 27, 2008

Last Modified

April 23, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-31649✓ verified
    First seen Apr 14, 2008

    Cezanne 7 - '/CznCommon/CznCustomContainer.asp?FUNID' SQL Injection

    Open source ↗
  • Exploit-DBEDB-31648✓ verified
    First seen Apr 14, 2008

    Cezanne 7 - 'cflookup.asp?FUNID' SQL Injection

    Open source ↗

Frequently asked(4)

What is CVE-2008-1968?
CVE-2008-1968 is a none vulnerability published on April 27, 2008. Multiple SQL injection vulnerabilities in Cezanne 7 allow remote authenticated users to execute arbitrary SQL commands via the FUNID parameter to (1) CFLookup.asp and (2) CznCommon/CznCustomContainer.asp.
When was CVE-2008-1968 disclosed?
CVE-2008-1968 was first published in the National Vulnerability Database on April 27, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-1968 actively exploited?
CVE-2008-1968 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2008-1968?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-1968, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2008-1968

Explore →

Is Your Infrastructure Affected by CVE-2008-1968?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.