dbcve.org
RedirectsWordPress extension · Declaire

CVE-2024-1566

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to after 1.2.1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Redirects plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save function in all versions up to, and including, 1.2.1. This makes it possible for unauthenticated attackers to change redirects created with this plugin. This could lead to undesired redirection to phishing sites or malicious web pages.

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 confidence

The Redirects WordPress plugin has a broken access control vulnerability in its save function. The function lacks both a capability check to verify the user has appropriate admin privileges and nonce verification to prevent CSRF attacks. This allows any unauthenticated visitor to send a request directly to the save endpoint and modify redirect configurations, changing where users are redirected when visiting certain URLs.

MitigationUpdate to a patched version of the plugin once available. Until then, consider disabling the plugin or using a WAF to block unauthorized save requests to the admin-ajax.php or admin-post.php endpoints.

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
RedirectsWordPress extension
Affected:<= 1.2.1

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Declaire Redirects plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'demaire-redirects' or similar
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, view the plugin details to see the version number, or open the plugin's main PHP file and check the 'Version' header in the plugin comment block
    Affected if Version displayed is 1.2.1 or lower
  3. Confirm the save endpoint exists and is accessible
    Check if the plugin registers AJAX handlers (admin-ajax.php?action=redirects_save or similar) or admin-post.php handlers for save operations. Inspect the plugin source code for the save function handling POST requests
    Affected if The save function handles requests without checking user capabilities or verifying nonces
  4. Test for unauthenticated access to save functionality
    Send a crafted POST request to the plugin's save endpoint (typically admin-ajax.php with the plugin's action parameter) without providing authentication cookies or nonce tokens
    Affected if The server accepts and processes the request without returning an authentication error or requiring admin privileges
  5. Verify redirect configurations can be modified
    After confirming unauthenticated access, inspect the WordPress database wp_options table for redirect-related entries, or check if new redirect rules were created after an unauthenticated request
    Affected if Redirect rules were created or modified without authentication

A user is affected if the Declaire Redirects plugin version is 1.2.1 or lower and the save endpoint accepts unauthenticated requests without capability or nonce verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.2.1
Interim mitigation

Update to a patched version of the plugin once available. Until then, consider disabling the plugin or using a WAF to block unauthorized save requests to the admin-ajax.php or admin-post.php endpoints.

Fix this in Redirects Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1566 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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