Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress two-factor-authentication plugin before version 1.1.10. The reported issue is cross-site scripting in the admin area. Business urgency depends on whether the plugin is installed and outdated; the public record does not provide CVSS, exploit details, or confirmed active abuse.
Executive priority
Treat this as a targeted hygiene item, not an emergency based on current evidence. Prioritize remediation on internet-facing WordPress sites where the affected plugin is installed and outdated.
Technical view
CVE-2015-9355 describes an XSS flaw in the admin area of the two-factor-authentication WordPress plugin before 1.1.10. The sources do not specify the vulnerable parameter, required privileges, user interaction, payload constraints, CWE, or CVSS score.
Likely exposure
Exposure is likely limited to WordPress sites running the two-factor-authentication plugin below 1.1.10. The source bundle does not identify CPEs, hosting environments, or broader affected products.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Public evidence here is sparse and does not include exploit availability or attack prerequisites.
Researcher notes
The available record is minimal: XSS, admin area, plugin versions before 1.1.10. Avoid assuming stored versus reflected XSS, authentication requirements, or exploitability without additional vendor or code evidence.
Mitigation direction
- Upgrade the plugin to version 1.1.10 or later where available.
- Check the WordPress plugin developer changelog for current vendor guidance.
- Disable the plugin if it cannot be updated promptly.
- Limit WordPress admin access to trusted users only.
Validation and detection
- Inventory WordPress sites for the two-factor-authentication plugin.
- Confirm each installed plugin version is 1.1.10 or later.
- Review admin-area access logs for unusual activity.
- Verify no unsupported fork or renamed copy is deployed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2015-9355 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/two-factor-authentication/#developersCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.