How severe is CVE-2005-3963?

CVE-2005-3963 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-3963 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-3963?

CVE-2005-3963 primarily affects Dotclear. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-3963?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-3963 published?

CVE-2005-3963 was published on 2005-12-02 and last updated on 2026-06-16.

CVE-2005-3963

CVE-2005-3963 is a high-severity vulnerability in Dotclear with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (69th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Dotclear
Published: 2005-12-02
Last modified: 2026-06-16

Description

SQL injection vulnerability in session.php in DotClear before 1.2.3 allows remote attackers to execute arbitrary SQL commands via the dc_xd parameter in a cookie.

Frequently asked questions

What is CVE-2005-3963?: SQL injection vulnerability in session.php in DotClear before 1.2.3 allows remote attackers to execute arbitrary SQL commands via the dc_xd parameter in a cookie.
How severe is CVE-2005-3963?: CVE-2005-3963 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-3963 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-3963?: CVE-2005-3963 primarily affects Dotclear. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-3963?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-3963 published?: CVE-2005-3963 was published on 2005-12-02 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:dotclear:dotclear:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:dotclear:dotclear:1.2.2:*:*:*:*:*:*:*

More vulnerabilities in Dotclear

CVE-2005-3957 — Critical (CVSS 10.0): Unspecified vulnerability in the Trackback functionality in DotClear 1.2.1 has unknown impact and attack vectors.
CVE-2008-3232 — Critical (CVSS 9.3): Unrestricted file upload vulnerability in ecrire/images.php in Dotclear 1.2.7.1 and earlier allows remote authenticated…
CVE-2023-53952 — High (CVSS 8.8): Dotclear 2.25.3 contains a remote code execution vulnerability that allows authenticated attackers to upload malicious…
CVE-2024-58281 — High (CVSS 8.8): Dotclear 2.29 contains a remote code execution vulnerability that allows authenticated attackers to upload malicious…
CVE-2015-8832 — High (CVSS 8.8): Multiple incomplete blacklist vulnerabilities in inc/core/class.dc.core.php in Dotclear before 2.8.2 allow remote…
CVE-2016-7902 — High (CVSS 8.8): Unrestricted file upload vulnerability in the fileUnzip->unzip method in Dotclear before 2.10.3 allows remote…

All CVEs affecting Dotclear →