SecurityWordPress extension · Ithemes
CVE-2018-7433
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 · uneditedThe iThemes Security plugin before 6.9.1 for WordPress does not properly perform data escaping for the logs page.
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 · high confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in the iThemes Security plugin for WordPress. The logs page fails to properly escape data before rendering it, allowing an attacker to inject malicious JavaScript that executes in the browser of administrators viewing the logs. The CVSS 7.5 indicates high severity due to the potential for session hijacking or administrative account compromise.
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
SecurityWordPress extension
<= 6.9.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify iThemes Security plugin installationCheck the WordPress plugins directory or admin panel for the presence of the iThemes Security plugin. In the file system, this is typically located at /wp-content/plugins/ithemes-security/ or check via WordPress admin under Plugins > Installed Plugins.Affected if The iThemes Security plugin is not installed on the WordPress site.
-
Determine installed version of iThemes SecurityIn WordPress admin, go to Plugins > Installed Plugins and look for the iThemes Security entry to see the version number. Alternatively, check the main plugin file (usually ithemes-security.php or plugin-name.php) in the plugin directory for the Version header comment.Affected if The installed version is 6.9.0 or earlier.
-
Verify access to the logs pageIn the WordPress admin sidebar, look for the iThemes Security menu item and navigate to the Logs section (or Security > Logs). This page displays security event logs.Affected if The logs page is accessible and displays security event data.
-
Inspect logs page for unescaped outputView the HTML source of the logs page in a browser (right-click > View Page Source) and look for any log entries that contain unescaped HTML or JavaScript. Specifically check if user-supplied data in log entries renders as raw HTML rather than being escaped.Affected if Log entries display raw HTML characters or unescaped user input is visible in the page source.
A user is affected if iThemes Security version 6.9.0 or earlier is installed and the logs page is accessible to administrators.
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 dataUpgrade iThemes Security plugin to version 6.9.1 or later which contains proper data escaping for the logs page.
Fix this in Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7433 — 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-2018-7433 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