CVE-2026-32541
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 · uneditedMissing Authorization vulnerability in Premmerce Premmerce Redirect Manager premmerce-redirect-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Premmerce Redirect Manager: from n/a through <= 1.0.12.
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 confidenceMissing Authorization vulnerability in Premmerce Redirect Manager WordPress plugin allows unauthenticated or unauthorized users to exploit incorrectly configured access control security levels, potentially enabling creation, modification, or deletion of redirects without proper permissions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Premmerce Redirect Manager is installedCheck for the plugin directory at wp-content/plugins/premmerce-redirect-manager/ and verify the main plugin file existsAffected if The plugin directory and main PHP file exist in the WordPress plugins folder
-
Identify the installed versionOpen the main plugin PHP file and look for the 'Version' header in the plugin comment block, or check the plugin admin pageAffected if The version cannot be determined or is within an affected range (contact vendor for specific vulnerable versions)
-
Verify redirect management functionality existsSearch plugin files for functions that create, modify, or delete redirects (look for 'add_redirect', 'update_redirect', 'delete_redirect', or similar action handlers)Affected if Redirect management functions exist in the plugin code
-
Inspect AJAX handlers for missing capability checksExamine PHP files containing wp_ajax_ hooks related to redirects; verify each handler calls current_user_can() or a similar capability check before processing the requestAffected if AJAX action handlers exist that process redirect data without verifying user capabilities
-
Check admin page handlers for authorization gapsReview admin action handlers (admin_init, admin_post) that process redirect creation, modification, or deletion; confirm they validate user permissionsAffected if Admin handlers process redirect operations without proper authorization checks
A user is affected if Premmerce Redirect Manager plugin is installed and its AJAX or admin handlers process redirect operations without verifying that the requesting user has appropriate permissions (e.g., manage_options capability).
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 capability checks and nonce verification on all sensitive AJAX and admin actions; update to a patched version if available from the vendor.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32541 — 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-2026-32541 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