How severe is CVE-2005-1840?

CVE-2005-1840 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2005-1840 being actively exploited?

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

What products are affected by CVE-2005-1840?

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

How do I fix CVE-2005-1840?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-1840 published?

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

CVE-2005-1840

CVE-2005-1840 is a medium-severity vulnerability in Phpcms with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 2% (76th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phpcms
Published: 2005-06-02
Last modified: 2026-06-16

Description

Directory traversal vulnerability in class.layout_phpcms.php in phpCMS 1.2.x before 1.2.1pl2 allows remote attackers to read or include arbitrary files, as demonstrated using a .. (dot dot) in the language parameter to parser.php.

Frequently asked questions

What is CVE-2005-1840?: Directory traversal vulnerability in class.layout_phpcms.php in phpCMS 1.2.x before 1.2.1pl2 allows remote attackers to read or include arbitrary files, as demonstrated using a .. (dot dot) in the language parameter to parser.php.
How severe is CVE-2005-1840?: CVE-2005-1840 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2005-1840 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-1840?: CVE-2005-1840 primarily affects Phpcms. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-1840?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-1840 published?: CVE-2005-1840 was published on 2005-06-02 and last updated on 2026-06-16.

References

Affected products (4)

cpe:2.3:a:phpcms:phpcms:1.2.0:*:*:*:*:*:*:*
cpe:2.3:a:phpcms:phpcms:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:phpcms:phpcms:1.2.1_p12:*:*:*:*:*:*:*
cpe:2.3:a:phpcms:phpcms:1.2.1_pl1:*:*:*:*:*:*:*

More vulnerabilities in Phpcms

CVE-2020-22203 — Critical (CVSS 9.8): SQL Injection in phpCMS 2008 sp4 via the genre parameter to yp/job.php.
CVE-2020-22199 — Critical (CVSS 9.8): SQL Injection vulnerability in phpCMS 2007 SP6 build 0805 via the digg_mod parameter to digg_add.php.
CVE-2018-19127 — Critical (CVSS 9.8): A code injection vulnerability in /type.php in PHPCMS 2008 allows attackers to write arbitrary content to a website…
CVE-2020-22201 — High (CVSS 8.8): phpCMS 2008 sp4 allowas remote malicious users to execute arbitrary php commands via the pagesize parameter to…
CVE-2008-0513 — High (CVSS 7.8): Directory traversal vulnerability in parser/include/class.cache_phpcms.php in phpCMS 1.2.2 allows remote attackers to…
CVE-2018-14940 — High (CVSS 7.5): PHPCMS 9 allows remote attackers to cause a denial of service (resource consumption) via large font_size, height, and…

All CVEs affecting Phpcms →