Solid SecurityWordPress extension · Solidwp
CVE-2023-28786
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in SolidWP Solid Security – Password, Two Factor Authentication, and Brute Force Protection.This issue affects Solid Security – Password, Two Factor Authentication, and Brute Force Protection: from n/a through 8.1.4.
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 confidenceThis is an Open Redirect vulnerability in the SolidWP Solid Security WordPress plugin (formerly iThemes Security). The vulnerability allows an attacker to craft malicious URLs that appear to point to the legitimate site but actually redirect users to an attacker-controlled domain. This can be exploited in phishing attacks to increase their credibility and bypass user skepticism.
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
Solid SecurityWordPress extension
<= 8.1.4CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Check plugin version in WordPress adminLog into WordPress admin, go to Plugins > Installed Plugins, find 'SolidWP Solid Security' (or iThemes Security), and note the version number displayedAffected if The displayed version is 8.1.4 or lower
-
Check version via WP-CLIRun command: wp plugin list --name='solid-security' --format=table or wp plugin list --name='ithemes-security' --format=tableAffected if The version column shows 8.1.4 or lower
-
Check version via plugin fileAccess the WordPress site via FTP or file manager, navigate to /wp-content/plugins/solid-security/ (or ithemes-security/), open readme.txt and find the 'Stable tag' line, or check the plugin header in the main PHP fileAffected if The stable tag or version in the plugin header is 8.1.4 or lower
-
Verify plugin is activeIn WordPress admin Plugins page, confirm the Solid Security plugin shows as 'Active'Affected if The plugin is active and the version is 8.1.4 or lower - the open redirect can be exploited
If SolidWP Solid Security (or iThemes Security) plugin is installed and active at version 8.1.4 or lower, the environment is affected by this open redirect vulnerability.
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 SolidWP Solid Security plugin to version 8.1.5 or later to patch the open redirect vulnerability.
Fix this in Solid Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28786 — 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-28786 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