CVE-2012-1565
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 · uneditedUnspecified vulnerability in ez Publish 4.1.4, 4.2, 4.3, 4.4, 4.5, and 4.6 has unknown impact and attack vectors related to an insecure direct object reference.
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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability in ez Publish CMS allows unauthorized access to data or functionality by manipulating direct object references (such as database IDs in URLs or parameters). The specific attack vector is unspecified, but IDOR typically enables attackers to bypass authorization and access or modify resources belonging to other users.
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= 4.1.4= 4.2.0= 4.3.0= 4.4.0= 4.5.0= 4.6.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
- 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.
-
Identify installed ez Publish versionLocate the version file or check the admin interface: look for version.php in the installation root, or log into the admin dashboard and navigate to Setup > Classes or System Information to view the version numberAffected if the installed version matches 4.1.4, 4.2.0, 4.3.0, 4.4.0, 4.5.0, or 4.6.0 exactly
-
Inventory endpoints accepting object IDsReview the application for URL parameters or form fields that accept direct object identifiers (such as contentobject_id, node_id, or similar ID parameters in the query string or POST data)Affected if the application uses direct object references in URLs or parameters without obvious access control indicators
-
Verify authorization on object accessTest accessing objects belonging to one user while authenticated as a different user, by modifying ID parameters in the URL or request. Check if the application validates that the authenticated user has permission to access the specific object before returning dataAffected if objects are returned without verifying the current user owns or has permission to access that specific object ID
-
Review module configuration for IDOR-prone featuresExamine content modules, comment sections, user profile pages, or file download handlers that may accept object IDs. Check if these modules implement ownership verification before displaying or modifying contentAffected if any module accepts direct object IDs and returns data without checking user permissions
A user is affected if running ez Publish version 4.1.4 through 4.6.0 AND the application has endpoints that accept direct object references without proper ownership validation
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 proper authorization checks on all object references and validate that the current user has permission to access the requested resource. Consider replacing direct object references with indirect references (mapping internal IDs to random tokens).
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1565 — 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-2012-1565 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