CVE-2023-49845
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 mattdeclaire Redirects redirects allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Redirects: from n/a through <= 1.2.1.
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 confidenceThe Redirects WordPress plugin by mattdeclaire has a Missing Authorization vulnerability (CVE-2023-49845) affecting versions up to 1.2.1. The plugin fails to properly enforce authorization checks before allowing users to modify redirect configurations, enabling attackers to exploit incorrectly configured access control security levels. This allows unauthorized modification of redirect rules, potentially leading to malicious redirects or traffic manipulation.
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 Redirects plugin installationCheck if the Redirects plugin by mattdeclaire is installed in your WordPress environment. This can be done by accessing the WordPress admin dashboard under Plugins, or by checking for the plugin directory in wp-content/plugins/Affected if The plugin is present in the WordPress installation
-
Determine installed plugin versionLocate the main plugin file (typically redirect.php or similar in the plugin directory) and check the version number declared in the plugin header comment. Alternatively, view the version in the WordPress Plugins admin pageAffected if The installed version is 1.2.1 or any version up to 1.2.1
-
Confirm plugin activation statusCheck if the Redirects plugin is currently activated in your WordPress site through the Plugins admin page or by querying the wp_options table for the active_plugins optionAffected if The plugin is installed and activated
-
Assess authorization configurationReview the plugin settings and code to determine what capability or role is required to modify redirect rules. Check if the plugin properly validates user capabilities (such as manage_options) before allowing redirect configuration changesAffected if The plugin allows any authenticated user with contributor-level access or higher to modify redirects without proper capability verification
Your environment is affected if the Redirects plugin is installed, active, and runs version 1.2.1 or below without proper capability checks before allowing redirect modifications.
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 Redirects plugin to a version beyond 1.2.1 if available. If no patched version exists, audit user roles with access to the plugin and implement proper WordPress capability checks (e.g., 'manage_options') before allowing redirect modifications.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49845 — 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-49845 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