CVE-2023-23888 is a high severity path traversal flaw (CVSS 7.6) in the Rank Math SEO WordPress plugin, affecting every version through 1.0.107.2. Update to 1.0.107.3 or later. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.
What's affected
- Rank Math SEO plugin, all versions up to and including 1.0.107.2, per the record and the Patchstack listing.
- Fixed version: 1.0.107.3, per Patchstack.
- Patchstack titles the issue local file inclusion, and classes it under the OWASP Top 10 injection category.
- Severity: CVSS 3.1 score 7.6 High, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L.
How to check if you're exposed
If you manage the site with WP-CLI, list the plugin and its version:
wp plugin list --fields=name,version,status | grep -i seo-by-rank-math
The plugin directory slug is seo-by-rank-math. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the Rank Math SEO entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.
The directory slug for Rank Math SEO is seo-by-rank-math.
What to do now
- Find every WordPress site that has Rank Math SEO installed, including staging copies, and read the version.
- Update the plugin to 1.0.107.3 or later and confirm the version in the plugin list.
- If you cannot update right away, deactivate the plugin until you can.
- Review web server logs for unexpected requests to the plugin around the time you learned of the issue.
Why it matters
The weakness is path traversal (CWE-22 (Path Traversal)). The plugin builds a file path from input without limiting it to the intended directory, so a request can reach files outside that folder. Patchstack describes the issue as local file inclusion, which means the server may read or include a file from its own disk.
The vector requires a low privilege account and rates confidentiality impact high, with low integrity and availability impact. Config files and credentials live on disk beside WordPress, so reading arbitrary local files can expose database passwords and keys. If you update, also consider whether any credentials on the host should be rotated. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
Plugin flaws are a supply chain problem as much as a coding problem. A WordPress site often runs dozens of third party plugins, each maintained by a different team, and each with its own release schedule. The practical defence is an inventory you trust and a habit of applying updates promptly.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is this remote?
The vector is network based but needs a low privilege account.
Should I rotate secrets after updating?
If your logs show suspicious requests to the plugin, yes. Otherwise a routine update is the proportionate response.
Sources
Last reviewed: 19 October 2026.