dbcve.org
Simple Mobile Url RedirectWordPress extension · Ozette

CVE-2023-23897

HIGH · 8.8 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to after 1.7.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Ozette Plugins Simple Mobile URL Redirect plugin <= 1.7.2 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 · low confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Simple Mobile URL Redirect WordPress plugin versions 1.7.2 and below allows attackers to induce authenticated administrators to perform unintended actions via maliciously crafted requests.

MitigationUpdate the plugin to a version newer than 1.7.2 which includes proper anti-CSRF token validation; if no update is available, disable the plugin until a patch is released.

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
Simple Mobile Url RedirectWordPress extension
Affected:<= 1.7.2

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
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 checks

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

  1. Locate the plugin directory
    Check your WordPress installation at wp-content/plugins/ for a folder named 'simple-mobile-url-redirect' or similar variant containing 'simple-mobile-url-redirect' in the name
    Affected if The plugin directory exists in the plugins folder
  2. Identify the installed version
    Open the main plugin PHP file (usually simple-mobile-url-redirect.php) and locate the version comment in the file header, or check the plugin's readme.txt file for the 'Stable tag' entry
    Affected if The version reported is 1.7.2 or any version lower (e.g., 1.7.1, 1.7.0, 1.6.x)
  3. Verify the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins' to see if the plugin is enabled
    Affected if The plugin appears in the list of active plugins and is currently enabled

You are affected if the Simple Mobile URL Redirect plugin is installed, active, and running at version 1.7.2 or below.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.7.2
Interim mitigation

Update the plugin to a version newer than 1.7.2 which includes proper anti-CSRF token validation; if no update is available, disable the plugin until a patch is released.

Recommended fix Moderate confidence

Upgrade to the latest available version of Simple Mobile URL Redirect plugin (version newer than 1.7.2)

  1. 1. Visit the WordPress plugin repository or the official Ozette Plugins website to check for available updates to the Simple Mobile URL Redirect plugin.
  2. 2. If a newer version than 1.7.2 is available, update the plugin through the WordPress admin dashboard under Plugins > Installed Plugins.
  3. 3. Alternatively, navigate to Dashboard > Updates and check for available plugin updates.
  4. 4. After updating, verify the plugin functionality works as expected on your site.
  5. 5. Test that the CSRF protection is functioning by confirming the plugin's settings can only be modified with valid authentication tokens.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simple Mobile Url Redirect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23897 — 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-2023-23897 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