CVE-2005-2893: Direct static code injection vulnerability in setcookie.php in PBLang 4.65, and possibly earlier versions, all

This month

HIGH 7.5DOWNGRADE

CVE-2005-2893 is a high-severity flaw (CVSS 7.5) affecting pblang. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Direct static code injection vulnerability in setcookie.php in PBLang 4.65, and possibly earlier versions, allows remote attackers to execute arbitrary PHP code via the username (u parameter), which is directly injected into a file that is later executed upon login.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.7% (top 14%)
CISA exploited list	No
Published	2005-09-14
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: pblang

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-09-14 20:03 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

pblang pblang DOWNGRADE

Affected: 4.65

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.65

1. Check installed version

apt-cache policy pblang || rpm -q pblang || pblang --version

2. No fixed release: DOWNGRADE to a release before 4.65 (Debian / Ubuntu)

apt-cache madison pblang sudo apt install pblang=<VERSION_BEFORE_4.65> sudo apt-mark hold pblang

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pblang sudo dnf downgrade pblang-<VERSION_BEFORE_4.65> sudo dnf versionlock add pblang

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-2893?

pblang: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2893 being exploited?

CVE-2005-2893 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-2893 affect?

CVE-2005-2893 affects pblang. Severity is high (CVSS 7.5). Direct static code injection vulnerability in setcookie.php in PBLang 4.65, and possibly earlier versions, allows remote attackers to execute arbitrary PHP code via the username (u parameter), which is directly injected into a file that is

How urgent is CVE-2005-2893?

Priority 53/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2007-3096 MEDIUM 6.8 UPGRADE Directory traversal vulnerability in login.php in PBLang (PBL) 4.67.16.a and earlier, when magic_quotes_gpc is
CVE-2007-1052 HIGH 10.0 UPGRADE PHP remote file inclusion vulnerability in index.php in PBLang (PBL) 4.60 and earlier allows remote attackers
CVE-2006-5062 HIGH 7.5 UPGRADE PHP remote file inclusion vulnerability in templates/pb/language/lang_nl.php in PBLang (PBL) 4.66z and earlier
CVE-2005-2895 MEDIUM 5.0 DOWNGRADE setcookie.php in PBLang 4.65, and possibly earlier versions, allows remote attackers to obtain sensitive infor
CVE-2005-2894 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in the user registration in PBLang 4.65, and possibly earlier version

References

← Back to latest CVEs