CVE-2005-2565
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGravity Board X (GBX) 1.1 allows remote attackers to obtain sensitive information via (1) a 1 in the perm parameter to deletethread.php or a direct request to (2) ban.php, (3) addnews.php, (4) banned.php, (5) boardstats.php, (6) adminform.php, (7) /forms/admininfo.php, (8) /forms/announcements.php, (9) forms/banform.php, or (10) other pages in the /forms directory, which reveal the path in an error message.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGravity Board X 1.1 contains multiple path disclosure vulnerabilities where direct requests to specific PHP files (deletethread.php with perm parameter, ban.php, addnews.php, banned.php, boardstats.php, adminform.php, and files in /forms directory) reveal full server file paths in error messages. This information disclosure enables attackers to gather reconnaissance data for more targeted attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Gravity Board X installationCheck for the presence of Gravity Board X by looking for typical installation directories such as /gbx, /forum, or /board, and look for an index.php file containing 'Gravity Board X' in the source code or a version file indicating version 1.1Affected if Gravity Board X version 1.1 is installed on the server
-
Identify vulnerable PHP filesCheck for the existence of the following files in the web root: deletethread.php, ban.php, addnews.php, banned.php, boardstats.php, adminform.php, and any PHP files in a /forms subdirectoryAffected if Any of these specific PHP files exist in the Gravity Board X installation
-
Verify PHP error display is enabledCheck the PHP configuration file (php.ini) for the setting 'display_errors = On' or check individual site configuration files for this directiveAffected if PHP display_errors is set to On, allowing error messages to be shown to users
-
Test for path disclosureMake a direct HTTP request to one of the affected files with malformed input - for deletethread.php, request it with a non-numeric or missing 'perm' parameter (e.g., /deletethread.php?perm=invalid)Affected if The response contains a full server file path such as /home/username/public_html/forum/includes/file.php on line XX
You are affected if Gravity Board X 1.1 is installed, the vulnerable PHP files are present, and PHP error display is enabled - the path disclosure can be confirmed by triggering an error on any of the listed files and observing if a full server file path appears in the error message.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement custom error handling to suppress verbose PHP error messages and display generic error pages instead. Alternatively, upgrade to a patched version of GBX if available, or disable PHP error display on production servers.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2565 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-2565 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data