CVE-2005-4856
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 · uneditedThe admin interface in eZ publish 3.5 before 3.5.7, 3.6 before 3.6.5, 3.7 before 3.7.3, and 3.8 before 20051110 does not properly handle authorization errors, which allows remote attackers to obtain sensitive information and see the admin pagelayout and associated templates via a request with (1) "anything after the url" or (2) a "wrong url".
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 confidenceThe admin interface in eZ publish versions 3.5 before 3.5.7, 3.6 before 3.6.5, 3.7 before 3.7.3, and 3.8 before 20051110 fails to properly handle authorization errors, allowing unauthenticated remote attackers to view sensitive admin page layouts and internal templates by requesting URLs with arbitrary paths or malformed URLs.
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<= 3.8.0= 3.5.0= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.6.0= 3.6.1= 3.6.2= 3.6.3CVSS 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.
-
Locate eZ publish installationSearch the web root directory for eZ publish by looking for index.php that contains 'eZ publish' or directories named 'ezpublish', 'ez' or 'kernel'. Common paths include /var/www/html/ or similar web directories.Affected if eZ publish is found on the system
-
Identify eZ publish versionCheck for version.php in the eZ publish directory, typically found in the kernel/classes/ directory or in the root index.php file. Open the file and look for a version number in the format X.Y.Z or a date like YYYYMMDD.Affected if The version number is 3.5.0 through 3.5.6, 3.6.0 through 3.6.3, 3.7.0 through 3.7.2, or 3.8.0 with a date before 20051110
-
Identify admin interface URL pathReview the eZ publish configuration files (site.ini or similar) or common admin paths. Typical admin paths include /ezadmin, /admin, /site_admin, or /ezpublish_admin. Check index.php for any admin-related path definitions.Affected if An admin interface path is defined in the configuration
-
Check if admin interface is network accessibleReview web server configuration (Apache nginx, IIS) for any rewrite rules or alias directives that expose the admin path externally. Verify the path is not restricted by IP, firewall, or HTTP authentication rules in the web server config.Affected if The admin interface URL path is accessible from untrusted networks without authentication
A user is affected if eZ publish is installed with a vulnerable version (3.5.x before 3.5.7, 3.6.x before 3.6.5, 3.7.x before 3.7.3, or 3.8.x before 20051110) AND the admin interface is network-accessible without authentication.
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 eZ publish 3.5.7, 3.6.5, 3.7.3, or 20051110 or later to obtain the vendor patch; alternatively, restrict admin interface access to trusted networks via firewall or web server access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4856 — 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-4856 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