Skip to main content
Mallory
MediumVulnerability

CVE-2008-2028: Information Disclosure in miniBB 2.2 via glang Parameter

Published Apr 30, 2008 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS2.2%83rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Minibb
IdentifiersCVE-2008-2028CWE-209

In miniBB 2.2, and possibly earlier versions, when PHP's register_globals is enabled, a remote attacker can trigger a full path disclosure by directly requesting the 'glang' parameter in a 'registernew' action to index.php. This results in an error message that reveals the full filesystem path of the application.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can obtain the full filesystem path of the miniBB installation. This information can be used to facilitate further attacks, such as local file inclusion or other path-based vulnerabilities, by providing knowledge of the server's directory structure.

Mitigation

If you can’t patch tonight, do this now.

Disable register_globals in the PHP configuration. Configure error reporting to avoid displaying sensitive information such as filesystem paths to users. Implement input validation and error handling to prevent path disclosure.

Remediation

Patch, then assume compromise.

Upgrade to a newer version of miniBB where this issue is resolved, or apply a patch that sanitizes error messages and does not disclose filesystem paths. Additionally, ensure that PHP's register_globals is disabled, as it is deprecated and insecure.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MinibbMinibbapplication
FAQ

Frequently asked questions

Is CVE-2008-2028 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-2028 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-2028?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2008-2028. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2008-2028?
Upgrade to a newer version of miniBB where this issue is resolved, or apply a patch that sanitizes error messages and does not disclose filesystem paths. Additionally, ensure that PHP's register_globals is disabled, as it is deprecated and insecure.
What products are affected by CVE-2008-2028?
Minibb.
How severe is CVE-2008-2028?
CVE-2008-2028 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 2.2% (83rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.