CVE-2005-4546
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 · uneditedsearch.php in eggblog 2.0 allows remote attackers to obtain the full path via an invalid q parameter, as used by the Keyword and Search fields, possibly due to an SQL injection vulnerability.
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 · moderate confidencesearch.php in eggblog 2.0 contains a vulnerability in handling the 'q' parameter (used by Keyword and Search fields) that allows remote attackers to obtain the full server path, potentially via improper input validation or an SQL injection flaw.
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<= 2.0CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 Eggblog is installedCheck your web server for the presence of eggblog files, typically in the web root or a subdirectory. Look for files like search.php, index.php, or configuration files that identify the software as eggblog.Affected if Eggblog files are found on the server in any accessible web directory
-
Identify the eggblog versionLocate the version information for your eggblog installation. Check README files, version comments in PHP files, or any version metadata within the eggblog directory structure. Compare the version number to 2.0.Affected if The installed version is 2.0 or any version lower than 2.0
-
Verify search.php exists and is accessibleLocate the search.php file within the eggblog installation directory. Confirm the file exists on the server and is accessible via HTTP/HTTPS through your web server.Affected if search.php exists in the eggblog installation and is web-accessible
-
Test the q parameter for path disclosureSend a crafted HTTP request to search.php with an unexpected value for the q parameter, such as a single quote ('), special characters, or an empty value. Inspect the server response for any leaked server file paths or error messages.Affected if The response reveals full server file paths or exposes system information not intended for public display
-
Check if keyword or search functionality is enabledVerify that the search feature is enabled on the eggblog site. This may be indicated by the presence of a search form or search-related database tables. The vulnerability affects the q parameter used by Keyword and Search fields.Affected if Search functionality is active and accessible to users on the deployed site
You are affected if eggblog version 2.0 or lower is installed, search.php is web-accessible, and the q parameter reveals server paths when supplied with unexpected input.
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 dataUpgrade to a patched version of eggblog or replace the software; implement proper input validation and parameterized queries in search.php to prevent path disclosure and SQL injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4546 — 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-4546 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