Redirect ManagerWordPress extension · Premmerce
CVE-2023-23787
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Premmerce Premmerce Redirect Manager plugin <= 1.0.9 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Premmerce Redirect Manager plugin for WordPress versions 1.0.9 and below. The lack of anti-CSRF tokens on state-changing operations (likely redirect creation/modification/deletion) allows attackers to trick authenticated administrators into performing unintended actions.
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
Redirect ManagerWordPress extension
<= 1.0.9CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 installedNavigate to WordPress Admin > Plugins or check the filesystem at wp-content/plugins/ for a directory named 'premmerce-redirect-manager' or similar premmerce prefix.Affected if The plugin directory exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually premmerce-redirect-manager.php) and locate the Version header in the plugin comment block, or check the version in the WordPress Plugins admin page.Affected if The reported version is 1.0.9 or lower (e.g., 1.0.8, 1.0.7, etc.)
-
Locate state-changing functionality in plugin codeSearch the plugin directory for files handling redirect operations - look for terms like 'create_redirect', 'update_redirect', 'delete_redirect', 'add_redirect', or form handlers in admin menu pages.Affected if Files exist that process redirect creation, modification, or deletion requests
-
Inspect redirect handlers for missing nonce verificationOpen the identified redirect handler files and search for absence of WordPress nonce functions: wp_nonce_field, check_admin_referer, wp_verify_nonce, or verify_nonce. Check form submission handlers and AJAX action callbacks.Affected if State-changing functions (redirect add/edit/delete) lack nonce verification calls like check_admin_referer() or wp_verify_nonce()
-
Verify admin access to redirect management interfaceLog into WordPress admin as an administrator and navigate to the Premmerce Redirect Manager menu (typically under Tools or a dedicated menu item) to confirm the redirect management UI is accessible.Affected if The redirect management interface is accessible to authenticated administrators
Your environment is affected if the Premmerce Redirect Manager plugin is installed with version 1.0.9 or lower and the code handling redirect operations lacks WordPress nonce verification on form submissions or AJAX requests.
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.
dbcve · scopedImplement WordPress nonces (nonce tokens) on all form submissions and AJAX requests that modify redirects, and verify the nonce validity server-side before executing any state-changing operation. Update to a patched version if available.
Version 1.1.0 or later (the first version after 1.0.9)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Premmerce Redirect Manager plugin
- 4. Check if an update is available and update to the latest version
- 5. If no update is available through WordPress, download the latest version from the WordPress plugin repository or contact Premmerce support
- 6. Verify the update was successful and test the redirect functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Redirect Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23787 — 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-2023-23787 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