Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2005-4687: PunBB 1.2.9, used alone or with F-ART BLOG:CMS, may trust a client's IP address as specified in the X-Forwarde

36
Routine
MEDIUM 5.0DOWNGRADEDOWNGRADE

CVE-2005-4687 is a medium-severity flaw (CVSS 5.0) affecting blog cms, punbb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PunBB 1.2.9, used alone or with F-ART BLOG:CMS, may trust a client's IP address as specified in the X-Forwarded-For HTTP header rather than the TCP/IP stack, which allows remote attackers to misrepresent their IP address by sending a modified header.

Why this priority

  • No elevated risk signals yet

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

Risk facts

CVSS score5.0 (Medium)
EPSS exploit chance1.4% (top 28%)
CISA exploited listNo
Published2005-12-31
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: f-art agency · punbb

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

f-art agency blog cms DOWNGRADE
Affected: 3.0 · 3.1 · 3.1.2 · 3.1.3 · 3.1.4 · 3.6.2 · 3.6.4 · 4.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0
1. Check installed version
apt-cache policy blog-cms || rpm -q blog-cms || blog-cms --version
2. No fixed release: DOWNGRADE to a release before 3.0 (Debian / Ubuntu)
apt-cache madison blog-cms sudo apt install blog-cms=<VERSION_BEFORE_3.0> sudo apt-mark hold blog-cms
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list blog-cms sudo dnf downgrade blog-cms-<VERSION_BEFORE_3.0> sudo dnf versionlock add blog-cms
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.
punbb punbb DOWNGRADE
Affected: 1.2.1 · 1.2.2 · 1.2.3 · 1.2.4 · 1.2.5 · 1.2.6 · 1.2.7 · 1.2.8
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.2.1
1. Check installed version
apt-cache policy punbb || rpm -q punbb || punbb --version
2. No fixed release: DOWNGRADE to a release before 1.2.1 (Debian / Ubuntu)
apt-cache madison punbb sudo apt install punbb=<VERSION_BEFORE_1.2.1> sudo apt-mark hold punbb
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list punbb sudo dnf downgrade punbb-<VERSION_BEFORE_1.2.1> sudo dnf versionlock add punbb
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-4687?

blog cms: downgrade or apply the listed mitigation; punbb: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-4687 being exploited?

CVE-2005-4687 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-4687 affect?

CVE-2005-4687 affects blog cms, punbb. Severity is medium (CVSS 5.0). PunBB 1.2.9, used alone or with F-ART BLOG:CMS, may trust a client's IP address as specified in the X-Forwarded-For HTTP header rather than the TCP/IP stack, which allows remote attackers to misrepresent their IP address by sending a modifi

How urgent is CVE-2005-4687?

Priority 36/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.