CVE-2005-1026: Multiple SQL injection vulnerabilities in SnailSource phpBB 2.0.x mods allow remote attackers to execute arbit

This month

HIGH 7.5DOWNGRADEDOWNGRADE

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

Multiple SQL injection vulnerabilities in SnailSource phpBB 2.0.x mods allow remote attackers to execute arbitrary SQL commands via the (1) file_id parameter to dlman.php in DLMan Pro or (2) id parameter to links.php in Linkz Pro (aka LinksLinks Pro).

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.4% (top 16%)
CISA exploited list	No
Published	2005-05-02
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: dlman pro · linkz pro

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

Am I affected?

Timeline

2005-05-02 04:00 UTCPublished CVE record published
2026-06-16 22:12 UTCUpdated Record last modified

dlman pro dlman pro DOWNGRADE

Affected: 0.9.8

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.9.8

1. Check installed version

apt-cache policy dlman-pro || rpm -q dlman-pro || dlman-pro --version

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

apt-cache madison dlman-pro sudo apt install dlman-pro=<VERSION_BEFORE_0.9.8> sudo apt-mark hold dlman-pro

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

dnf --showduplicates list dlman-pro sudo dnf downgrade dlman-pro-<VERSION_BEFORE_0.9.8> sudo dnf versionlock add dlman-pro

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.

linkz pro linkz pro DOWNGRADE

Affected: 1.0.3_beta2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.3_beta2

1. Check installed version

apt-cache policy linkz-pro || rpm -q linkz-pro || linkz-pro --version

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

apt-cache madison linkz-pro sudo apt install linkz-pro=<VERSION_BEFORE_1.0.3_beta2> sudo apt-mark hold linkz-pro

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

dnf --showduplicates list linkz-pro sudo dnf downgrade linkz-pro-<VERSION_BEFORE_1.0.3_beta2> sudo dnf versionlock add linkz-pro

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: phpBB 2.0.13 DLMan Pro Module - SQL Injection
Exploit-DB: phpBB 2.0.13 Linkz Pro Module - SQL Injection

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-1026?

dlman pro: downgrade or apply the listed mitigation; linkz pro: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1026 being exploited?

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

CVE-2005-1026 affects dlman pro, linkz pro. Severity is high (CVSS 7.5). Multiple SQL injection vulnerabilities in SnailSource phpBB 2.0.x mods allow remote attackers to execute arbitrary SQL commands via the (1) file_id parameter to dlman.php in DLMan Pro or (2) id parameter to links.php in Linkz Pro (aka Links

How urgent is CVE-2005-1026?

Priority 52/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

References

← Back to latest CVEs