CVE-2025-11532
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 Wisly plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0.0 due to missing validation on the 'wishlist_id' user controlled key. This makes it possible for unauthenticated attackers to remove and add items to other user's wishlists.
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 Wisly WordPress plugin up to version 1.0.0 contains an Insecure Direct Object Reference (IDOR) vulnerability due to insufficient validation of the user-controlled 'wishlist_id' parameter. This allows unauthenticated attackers to manipulate the wishlists of other users by adding or removing items through requests that reference arbitrary wishlist IDs without proper authorization checks.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Wisly plugin is installedCheck the WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard to see if the Wisly plugin appears in the list of installed plugins.Affected if The Wisly plugin is present in the WordPress installation.
-
Confirm installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, find the Wisly plugin and note the version number displayed below the plugin name. Alternatively, inspect the plugin main file header in wp-content/plugins/wishly/ to read the Version field.Affected if The installed version is 1.0.0 or any earlier version, since version 1.0.1 contains the fix.
-
Verify plugin is activeCheck the status column in Plugins > Installed Plugins. The plugin must be active for the vulnerable code to be executable.Affected if The Wisly plugin shows as Active.
-
Identify vulnerable endpoint exposureReview server access logs or use a web proxy to identify requests to wishlist-related AJAX actions (commonly wp-admin/admin-ajax.php?action=wishly_add_item or similar) that accept a wishlist_id parameter from unauthenticated sources.Affected if The site exposes an endpoint handling wishlist_id parameter without authentication or authorization verification.
A WordPress installation is affected if the Wisly plugin version 1.0.0 or earlier is installed, active, and exposes a wishlist endpoint that accepts unauthenticated requests with a user-controlled wishlist_id parameter.
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 Wisly plugin to version 1.0.1 or later which implements proper authorization validation on the wishlist_id parameter to ensure users can only modify their own wishlists, or remove the plugin until a patch is available.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11532 — 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-11532 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