Skip to main content
WordPress plugin recordReviewed

Kadence Security vulnerability records, including those titled iThemes Security and Solid Security

Titles in this history say iThemes Security, Solid Security and Better WP Security.

This page shows how to match a version on the fields, and where the plugin's module, lockout, two-factor and permission settings are read.

Kadence Security vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 19 records for Kadence Security. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 9.3.2

Worked out from data retrieved on .

Every affected range listed in this source for Kadence Security ends before version 9.3.2.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Solid Security <= 9.3.1 - IP Address Spoofing to Denial of Service

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 9.3.1

    Patched versions: 9.3.2

    Update to at least version 9.3.2.

  2. Solid Security Basic <= 9.0.0 - Unauthenticated Login Page Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 9.0.0

    Patched versions: 9.0.1

    Update to at least version 9.0.1.

  3. iThemes Security <= 8.1.4 - Open Redirection via redirect_to_https

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.7)
    Affected versions
    • All versions up to and including 8.1.4

    Patched versions: 8.1.5

    Update to at least version 8.1.5.

  4. iThemes Security < 7.9.1 and iThemes Security Pro < 6.8.4 - Hidden Login Bypass

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions before 7.9.1

    Patched versions: 7.9.1

    Update to at least version 7.9.1.

  5. iThemes Security <= 7.6.1 - Broken Password Mechanism

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 7.6.1

    Patched versions: 7.7.0

    Update to at least version 7.7.0.

Show 14 older records
  1. iThemes Security <= 7.0.2 - Authenticated SQL Injection

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 7.0.3

    Patched versions: 7.0.3

    Update to at least version 7.0.3.

  2. iThemes Security <= 6.9.0 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 6.9.0

    Patched versions: 6.9.1

    Update to at least version 6.9.1.

  3. iThemes Security <= 5.6.1 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions before 5.6.2

    Patched versions: 5.6.2

    Update to at least version 5.6.2.

  4. iThemes Security <= 5.6.1 - Sensitive Information Exposure via Diff Response

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 5.6.1

    Patched versions: 5.6.2

    Update to at least version 5.6.2.

  5. iThemes Security <= 5.3.5 - Missing Capabilities Check

    Published:
    Last updated:
    Severity:
    High (CVSS 7.4)
    Affected versions
    • All versions before 5.3.6

    Patched versions: 5.3.6

    Update to at least version 5.3.6.

  6. iThemes Security < 5.3.1 - Insecure Backup/Logfile Generation

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions before 5.3.1

    Patched versions: 5.3.1

    Update to at least version 5.3.1.

  7. iThemes Security < 5.3.5 - Authenticated Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Low (CVSS 3.3)
    Affected versions
    • All versions before 5.3.5

    Patched versions: 5.3.5

    Update to at least version 5.3.5.

  8. iThemes Security <= 4.6.12 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions before 4.6.13

    Patched versions: 4.6.13

    Update to at least version 4.6.13.

  9. Better WP Security <= 3.5.3 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 3.5.3

    Patched versions: 3.5.4

    Update to at least version 3.5.4.

  10. iThemes Security < 3.6.4 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 8.3)
    Affected versions
    • All versions before 3.6.4

    Patched versions: 3.6.4

    Update to at least version 3.6.4.

  11. Better WP Security <= 3.6.3 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 3.6.3

    Patched versions: 3.6.4

    Update to at least version 3.6.4.

  12. iThemes Security < 3.4.4 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions before 3.4.4

    Patched versions: 3.4.4

    Update to at least version 3.4.4.

  13. iThemes Security < 3.2.5 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 3.2.5

    Patched versions: 3.2.5

    Update to at least version 3.2.5.

  14. Better WP Security <= 3.2.4 - Multiple Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 3.2.4

    Patched versions: 3.2.5

    Update to at least version 3.2.5.

Check Kadence Security on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

Kadence Security's earlier names, and where the plugin takes input

Kadence Security is a security plugin published by Nexcess, with the WordPress.org slug better-wp-security.

Its listing says "Formerly iThemes Security", and the changelog there records "iThemes Security is now Solid Security!" under 9.0.0 and "Updated branding from SolidWP to Kadence" under 10.0.0. The listing says the plugin is free but offers additional paid commercial upgrades or support, and marks some features Pro, such as Version Management and Privilege Escalation.

It takes settings from the people who manage it, under Security > Settings, which the vendor's settings article divides into Global Settings, Features, User Groups, Notifications and Advanced Settings. Which roles may manage it is set per User Group, as the last check on this page shows.

It also reads requests from anyone: the article says the plugin relies on IP detection to identify visitors, apply firewall rules and enforce lockouts.

Kadence Security affected versions: match the fields, whatever name the title uses

Titles in the history call the plugin Solid Security, Solid Security Basic, iThemes Security and Better WP Security.

Cross-Site Scripting is a phrase that recurs, on some titles with Stored or Authenticated in front. Where a title states access, the wording includes Unauthenticated and Authenticated.

Read each record's affected range and patched versions field before its title. A search by CVE id misses the records that have none. The vendor's User Security article dates one feature to Solid Security Pro 8.2.0 and Solid Security Basic 9.2.0, a different number for each edition. Do not set a Pro version number against these ranges as if it were the free plugin's.

The changelog on the plugin's WordPress.org listing labels some entries Security, Security Hardening or Hardening. Those labels make it a second place to check before the update guidance at the top of the history is relied on. The records here are those the source data files under this slug. Examples whose titles use the words login, password and IP address:

  • CVE-2022-44593, whose title ends IP Address Spoofing to Denial of Service: all versions up to and including 9.3.1, with 9.3.2 in its patched versions field.
  • A record with no CVE id, whose title ends Unauthenticated Login Page Disclosure: all versions up to and including 9.0.0, with 9.0.1 in its patched versions field.
  • CVE-2020-36176, whose title ends Broken Password Mechanism: all versions up to and including 7.6.1, with 7.7.0 in its patched versions field. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
  • A record with no CVE id, titled iThemes Security < 7.9.1 and iThemes Security Pro < 6.8.4 - Hidden Login Bypass: its affected range is all versions before 7.9.1 and its patched versions field reads 7.9.1. The Pro number in the title is in neither field.

Reading Kadence Security's settings without changing them

The vendor's articles write each path from Security, as in Security > Settings > Features, and carry a notice that Solid Security is becoming Kadence Security and that you may see both names used.

A label quoted here as Solid Security may read Kadence Security on screen. Read each screen and leave without saving.

Version, edition and update control

The Description column of the WordPress Plugins screen includes each plugin's version number. 1 min read

Enabled modules, and what overrides them

The settings article divides Security > Settings > Features into four areas, Login Security, Firewall, Site Check and Utilities, each containing modules that can be turned on or off. 1 min read

Lockouts, brute force thresholds and the login address

The settings article gives the default configuration of Local Brute Force, a module in the Firewall area, as 5 failed attempts per host, or 10 per user account, for a temporary lockout of 15 minutes, with a permanent ban after 3 temporary lockouts within 7 days. 1 min read

Two-factor methods, and who is covered

Two Factor is a module in the Login Security area. 1 min read

Who can manage the plugin

User Groups also decides who administers the plugin. 1 min read

What a Kadence Security version match leaves unread

Setting the installed version beside the affected ranges in the history tells you whether a known record covers that release of the free plugin.

It does not tell you whether a flaw was used before the update, whether ITSEC_DISABLE_MODULES sits in wp-config.php, what Proxy Detection is set to, which groups hold Manage Solid Security, or whether an account has a temporary Privilege Escalation.

A WordPress security audit checks whether the login screen and the admin area can be reached from any address on the internet, and which restriction, if any, is in place. Where one exists, it records whether it also covers xmlrpc.php and the REST API rather than the login form alone, and it lists which accounts hold an application password.

Frequently asked questions

The source data files it here, and the name matches the plugin's slug. CVE-2012-4264 has a title that begins Better WP Security and ends Multiple Cross-Site Scripting: all versions up to and including 3.2.4, with 3.2.5 in its patched versions field. CVE-2012-4263, published the same day, has a title that begins iThemes Security and ends Cross-Site Scripting: all versions before 3.2.5, with the same patched version. The name in a title does not tell you which releases a record covers.

The records are those the source data files under better-wp-security, the slug of the free plugin's listing. Being filed there does not settle whether a record also applies to the Pro edition. The vendor's FAQ says Pro is downloaded from your account, installed and activated, after which the free version can be deactivated and deleted. Keep a Pro version number apart from the free plugin's when you read the affected ranges.

The WordPress Plugins screen displays an update notice when a plugin hosted in the Plugin Directory has a newer version available. Set the installed version against the update guidance at the top of the history. For Pro, the vendor's FAQ says the plugin needs to be licensed in order to receive updates, and gives the path WordPress Admin Bar > Settings > SolidWP Licensing.

The vendor's settings article says that after someone enters the custom login URL they are redirected back to the default WordPress login URL. The vendor's FAQ adds that reaching the login page through the custom slug sets a cookie for one hour, during which wp-login.php and wp-admin open in the same browser without it. Titles in this history include one ending Hidden Login Bypass and one ending Unauthenticated Login Page Disclosure. Neither names a setting, so match on the version fields.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 7 of the 19 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.