Security readout for executives and security teams
Plain-English summary
CVE-2019-19542 is a stored cross-site scripting issue in the WordPress ListingPro theme before version 2.0.14.2. If an affected site accepts new listing submissions, attacker-controlled content in the Good For field could be saved and later shown to users or administrators.
Executive priority
Treat as a targeted web-content integrity risk for affected WordPress properties. Prioritize sites that allow external listing submissions or have administrator review workflows exposed to submitted listing content.
Technical view
The CVE describes persistent XSS through the Good For field on the new listing submit page in ListingPro before 2.0.14.2. The bundle provides no CVSS, CWE, CPE, authentication requirement, exploit details, or confirmed impact scope beyond the affected theme and field.
Likely exposure
Exposure is limited to WordPress sites using the ListingPro theme before 2.0.14.2, especially where listing submission functionality is enabled or reachable.
Exploitation context
The source bundle does not identify active exploitation, public exploit code, or KEV listing. Risk comes from stored XSS persistence if submitted field content is later rendered in a privileged or user-facing context.
Researcher notes
Evidence is sparse. The bundle confirms product, fixed-version boundary, field, and vulnerability class, but not attack prerequisites, rendering context, privilege requirements, or severity scoring. Avoid assuming broader WordPress core exposure.
Mitigation direction
- Upgrade ListingPro to version 2.0.14.2 or later.
- Check vendor guidance for any additional cleanup steps.
- Temporarily restrict new listing submissions until patched.
- Review existing Good For field content for suspicious entries.
- Remove or sanitize untrusted listing content where appropriate.
Validation and detection
- Inventory WordPress sites using the ListingPro theme.
- Confirm the installed ListingPro version is 2.0.14.2 or later.
- Verify whether new listing submission pages are public or restricted.
- Review stored listing data in the Good For field.
- Check logs or moderation queues for suspicious listing submissions.
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-2019-19542 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://wpvulndb.com/vulnerabilities/9974CVE 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.