Security readout for executives and security teams
Plain-English summary
CVE-2016-11013 is a cross-site scripting issue in the WordPress wp-listings plugin before version 2.0.2. Affected sites may expose users or administrators to injected script when viewing listing content. The source bundle provides no CVSS score and no evidence of active exploitation.
Executive priority
Prioritize remediation for public WordPress sites using this plugin, especially if listings are edited by many users. The issue is not currently documented as exploited in the provided sources, but XSS can affect administrator sessions and site trust.
Technical view
The CVE describes XSS in includes/views/single-listing.php in wp-listings before 2.0.2. The available references identify the plugin developer page and a GitHub pull request, but the bundle does not include exploit details, a CWE, or a scored severity.
Likely exposure
Exposure is limited to WordPress sites running the wp-listings plugin before 2.0.2, especially where single listing pages are publicly reachable or editable by untrusted users.
Exploitation context
The source bundle does not show KEV listing or active exploitation. It only states that vulnerable versions have XSS in a single-listing view file.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, exploit status, or detailed advisory is included. Treat the version boundary and referenced pull request as the main technical anchors, and avoid assuming broader plugin impact beyond single-listing.php.
Mitigation direction
- Inventory WordPress sites for the wp-listings plugin and installed version.
- Upgrade wp-listings to version 2.0.2 or later where available.
- Review vendor changelog and GitHub PR for fix context.
- Restrict listing content editing to trusted users until remediated.
- Check vendor guidance if upgrading is not immediately possible.
Validation and detection
- Confirm wp-listings version is 2.0.2 or later.
- Verify public single listing pages still render correctly after update.
- Review WordPress roles allowed to create or edit listings.
- Check web logs and site content for unexpected script injection indicators.
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-2016-11013 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/wp-listings/#developersCVE reference · x_refsource_MISC
- https://github.com/agentevolution/wp-listings/pull/52CVE 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.