Security readout for executives and security teams
Plain-English summary
CVE-2019-15836 is a stored cross-site scripting issue in the wp-ultimate-recipe WordPress plugin before 3.12.7. If exploited, malicious content could be saved in the site and execute in visitors' or administrators' browsers. The public bundle does not provide severity scoring, affected inputs, or exploitation evidence.
Executive priority
Treat this as a moderate web application hygiene issue. Prioritize internet-facing WordPress sites, especially those with many content editors or stale plugins. There is no sourced evidence of active exploitation, but stored XSS can create persistent business risk if left unpatched.
Technical view
The CVE record describes stored XSS in wp-ultimate-recipe versions before 3.12.7. Stored XSS implies untrusted input is persisted and later rendered unsafely. The supplied sources do not identify the vulnerable field, required privileges, CVSS vector, CWE, or detailed remediation beyond the version boundary.
Likely exposure
Exposure is most likely on WordPress sites with wp-ultimate-recipe installed at a version earlier than 3.12.7. The bundle lists no CPEs or vendor metadata, so plugin inventory and WordPress admin checks are needed to confirm real exposure.
Exploitation context
No active exploitation is supported by the supplied sources, and the CVE is not marked in KEV. Stored XSS can still matter operationally because payloads may persist in content and affect later viewers, including privileged WordPress users.
Researcher notes
Evidence is sparse. The bundle confirms product, version boundary, and stored XSS class only. It does not provide vulnerable parameters, authentication requirements, exploit maturity, CVSS, or CWE. Avoid assuming broader WordPress impact beyond wp-ultimate-recipe before 3.12.7.
Mitigation direction
- Upgrade wp-ultimate-recipe to 3.12.7 or later if vendor guidance supports it.
- If no supported update is available, disable or remove the plugin pending vendor guidance.
- Restrict recipe creation and editing to trusted WordPress users.
- Review WordPress accounts for unauthorized editor or administrator access.
Validation and detection
- Inventory WordPress sites for wp-ultimate-recipe installations.
- Confirm installed plugin versions are not earlier than 3.12.7.
- Check whether the plugin is active or present in inactive plugin directories.
- Review recipe content for unexpected scripts or suspicious embedded markup.
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-15836 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/9394CVE reference · x_refsource_MISC
- https://wordpress.org/plugins/wp-ultimate-recipe/#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.