CVE-2008-2722
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 · uneditedMenalto Gallery before 2.2.5 allows remote attackers to bypass permissions for sub-albums via a ZIP archive.
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 confidenceMenalto Gallery before version 2.2.5 contains a permission bypass vulnerability in its ZIP archive handling. Remote attackers can craft or manipulate ZIP archives to bypass permission checks and access sub-albums they would normally not have authorization to view, exploiting how the software processes archived content during upload or extraction.
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.2.4= 2.1= 2.1.1= 2.1.2= 2.2.0= 2.2.1= 2.2.2= 2.2.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
- 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.
-
Determine installed Gallery versionLocate the version file or check the main configuration file for the Gallery version string (commonly found in version.php, config.php, or the database)Affected if The installed version matches 2.1, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.2.3, or any version 2.2.4 or lower
-
Verify ZIP archive upload feature is enabledCheck Gallery admin settings or module configuration for the ZIP upload or archive extraction module. Look for settings related to 'ZIP upload', 'archive import', or 'batch upload' functionalityAffected if The ZIP upload or archive import feature is enabled and accessible to users
-
Identify sub-album structure and permission boundariesReview the Gallery album hierarchy in the admin panel or database to determine which sub-albums exist and what permission restrictions are applied to themAffected if There are sub-albums with restricted access permissions separate from parent albums
-
Review recent ZIP-based uploadsCheck server logs, upload history, or the Gallery database for recent archive uploads that may contain sub-album content, focusing on uploads by users with limited permissionsAffected if Users with limited permissions have recently uploaded ZIP archives containing nested album structures
A user is affected if they run any Gallery version 2.2.4 or below (including 2.1.x and 2.2.x branches), have the ZIP archive upload feature enabled, and maintain sub-albums with restricted access permissions.
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 Gallery 2.2.5 or later to obtain the patched version that properly validates permissions when handling ZIP archives containing sub-album content.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2722 — 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-2008-2722 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