dbcve.org
Ez PublishApplication · Ez

CVE-2007-4493

HIGH · 10.0 CVSS v2.0 Published 2007-08-23
Fix available
A fix is available. Upgrade to after 3.8.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
eZ publish before 3.8.9, and 3.9 before 3.9.3, does not properly check permissions on module views that lack a policy function, which has unknown impact and attack vectors, as demonstrated by a vulnerability in the discount functionality in the shop module.

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 confidence

eZ publish before 3.8.9 and 3.9 before 3.9.3 contains an authorization bypass vulnerability where module views lacking a policy function do not undergo proper permission checks. This allows unauthenticated or unauthorized users to access restricted functionality, as demonstrated by the shop module's discount functionality.

MitigationUpgrade eZ publish to version 3.8.9, 3.9.3, or later. Until patched, disable or restrict access to the shop module and review all module views for properly defined policy functions.

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
Ez PublishApplication
Affected:<= 3.8.8= 3.9.0= 3.9.1= 3.9.2

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed eZ Publish version
    Locate the version file (typically version.php in the root directory or through the admin interface under 'Setup' > 'Versions'), or run a grep command: grep -r 'eZ Publish' /path/to/ezpublish/ | head -5
    Affected if The installed version is 3.8.8 or earlier, or 3.9.0, 3.9.1, or 3.9.2
  2. Verify if shop module is enabled
    Check the site.ini configuration file (typically in settings/site.ini or settings/override/site.ini) for ActiveModules[] and look for 'shop' in the list, or examine the /module/shop/ directory exists and is accessible
    Affected if The shop module is listed as active in the site configuration
  3. Inspect module view policy configurations
    Examine the access policy definitions in role-based access control (RBAC) settings through the admin interface under 'User' > 'Roles' or by reviewing policy.ini.append.php files in the module directories
    Affected if Module views (particularly shop/discount) lack defined policy functions or the policies are set to allow public access
  4. Review anonymous user role permissions
    Check the anonymous user role configuration in the admin interface under 'User' > 'Roles' > 'Anonymous' or in role configuration files to see what modules and views are accessible without authentication
    Affected if The anonymous (guest) role has permissions to access shop module views without proper function-level authorization checks

The environment is affected if running eZ Publish version 3.8.8 or earlier, or 3.9.0-3.9.2, with the shop module enabled and module views lacking proper policy function definitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.8.8
Interim mitigation

Upgrade eZ publish to version 3.8.9, 3.9.3, or later. Until patched, disable or restrict access to the shop module and review all module views for properly defined policy functions.

Recommended fix High confidence

eZ Publish 3.8.9 (for 3.8.x branch) or 3.9.3 (for 3.9.x branch), or latest stable 3.x release

  1. 1. Back up your current eZ Publish database and all files
  2. 2. Identify your current eZ Publish version (3.8.x or 3.9.x branch)
  3. 3. For 3.8.x branch users: upgrade to eZ Publish 3.8.9 or later (preferably latest 3.8 stable)
  4. 4. For 3.9.x branch users: upgrade to eZ Publish 3.9.3 or later (preferably latest 3.9 stable)
  5. 5. Alternatively, upgrade to the latest stable eZ Publish 3.x release available
  6. 6. Test the upgrade in a staging environment before deploying to production
  7. 7. Verify that the shop module discount functionality works correctly after upgrade
Caveat Minor version upgrades typically maintain compatibility but test thoroughly in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ez Publish Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4493 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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