CVE-2025-11701
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 Zip Attachments plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check as well as missing post status validation in the za_create_zip_callback function in all versions up to, and including, 1.6. This makes it possible for unauthenticated attackers to download attachments from private and password-protected posts.
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 confidenceThe Zip Attachments WordPress plugin (versions up to 1.6) has a broken access control vulnerability in the za_create_zip_callback function. The function lacks both a capability check to verify user permissions and post status validation to ensure the user can access the requested attachments. This allows unauthenticated attackers to download attachments from private and password-protected posts by directly referencing post IDs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify Zip Attachments plugin is installedCheck the WordPress plugin directory or wp-admin plugins list for 'Zip Attachments' or check the plugin file header in wp-content/plugins/zip-attachments/zip-attachments.phpAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionOpen wp-content/plugins/zip-attachments/zip-attachments.php and locate the 'Version' header in the plugin comment block, or view the version in the WordPress plugin admin panelAffected if Version is 1.6 or lower (versions 1.7 and later contain the fix)
-
Identify if the vulnerable za_create_zip_callback function existsSearch the plugin files for 'za_create_zip_callback' function definition, typically found in the main plugin PHP file, and verify it lacks capability checks (like current_user_can) and post status validationAffected if The function exists and processes attachment requests without verifying user permissions or post accessibility
-
Test unauthenticated access to the vulnerable endpointSend a crafted request to the WordPress AJAX endpoint (typically /wp-admin/admin-ajax.php?action=create_zip) with a private or password-protected post ID to see if attachments are returned without authenticationAffected if Attachments from private or password-protected posts can be downloaded without providing credentials or satisfying post access requirements
A user is affected if the Zip Attachments plugin versions 1.6 or lower are installed and the za_create_zip_callback function is accessible without authentication, allowing unauthorized download of attachments from restricted posts.
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 dataUpdate the plugin to version 1.7 or later when available. If no update exists, disable the plugin or implement manual access controls at the web server level to restrict access to the vulnerable endpoint.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11701 — 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-2025-11701 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