CVE-2005-2564
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 · uneditedDirect static code injection vulnerability in editcss.php in Gravity Board X (GBX) 1.1 allows remote attackers to execute arbitrary PHP code, HTML, and script via the csscontent parameter, which is directly inserted into the gbxfinal.css file.
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 confidenceA direct static code injection vulnerability exists in editcss.php of Gravity Board X 1.1 where the csscontent parameter is written directly to the gbxfinal.css file without any sanitization or validation, allowing attackers to inject arbitrary PHP code, HTML, or JavaScript that will be executed when the CSS file is served.
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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installation versionLocate the version file or index page of the installation and verify the installed version is 1.1. Check files like version.php, index.php, or a readme file for the version number.Affected if The installed version is Gravity Board X 1.1 exactly.
-
Verify editcss.php file existsSearch the web root directory for the file editcss.php. Common paths may include /editcss.php, /admin/editcss.php, or /forum/editcss.php depending on installation location.Affected if The editcss.php file exists in the web-accessible directory.
-
Check write permissions on gbxfinal.cssLocate the gbxfinal.css file (typically in the same directory as editcss.php or in a /css/ folder) and verify if the web server process has write permissions to this file.Affected if The gbxfinal.css file exists and is writable by the web server user.
-
Inspect gbxfinal.css for injected codeOpen gbxfinal.css in a text editor or download it via HTTP and examine the contents for any unexpected PHP code blocks (<?php ... ?>), suspicious JavaScript, or base64-encoded strings that do not resemble normal CSS.Affected if The file contains PHP code, suspicious script tags, or code that was not authored by the administrator.
-
Check HTTP access to editcss.phpAttempt to access editcss.php directly via HTTP (e.g., GET request to the full URL) to confirm the script is executable and returns a response.Affected if The script is accessible via HTTP and accepts parameters without authentication errors.
A system is affected if it runs Gravity Board X 1.1 with editcss.php present and accessible, and the gbxfinal.css file is writable or already contains injected code.
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 strict input validation and sanitization on the csscontent parameter before writing to CSS files, or disable the editcss.php functionality entirely if not required.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2564 — 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-2564 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