Two Factor AuthenticationWordPress extension · Simbahosting
CVE-2015-9355
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 two-factor-authentication plugin before 1.1.10 for WordPress has XSS in the admin area.
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 confidenceThe two-factor-authentication plugin for WordPress versions prior to 1.1.10 contains a Cross-Site Scripting (XSS) vulnerability in the admin interface. This allows an attacker to inject malicious scripts through unsanitized input fields within the plugin's admin area, potentially compromising administrator sessions or performing actions with admin privileges.
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
Two Factor AuthenticationWordPress extension
< 1.1.10CVSS 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.0/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.
-
Verify Simbahosting Two Factor Authentication plugin is installedNavigate to WordPress admin panel under Plugins or inspect the /wp-content/plugins/ directory for a folder containing 'two-factor' or 'two-factor-authentication' in the nameAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually two-factor-authentication.php or similar) and locate the version string in the plugin header comment, or view the version displayed in the WordPress Plugins admin pageAffected if Version information is readable in the plugin header or admin interface
-
Compare installed version against affected rangeCompare the identified version number to the affected range: versions prior to 1.1.10 are vulnerableAffected if Installed version is lower than 1.1.10 (for example: 1.1.9, 1.1.8, 1.0.x, etc.)
-
Confirm plugin is active on the siteCheck the WordPress Plugins admin page to verify the plugin status shows as 'Active'Affected if Plugin is installed and currently active
You are affected if the Simbahosting Two Factor Authentication plugin is installed, active, and the version is lower than 1.1.10
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 data1.1.10
Upgrade the two-factor-authentication plugin to version 1.1.10 or later to obtain the patched version that properly sanitizes user input in the admin area.
Fix this in Two Factor Authentication
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9355 — 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-2015-9355 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