CVE-2019-25743: WordPress Soliloquy Lite 2.5.6 Persistent Cross-Site Scripting
WordPress Soliloquy Lite 2.5.6 contains a persistent cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by inserting script tags in the post title field. Attackers can submit POST requests to the post editing endpoint with script payloads in the post_title parameter, which are stored and executed when users preview the post.
Security readout for executives and security teams
Plain-English summary
Soliloquy Lite 2.5.6 for WordPress allows an authenticated user to store script content in a post title. The script can run when another user previews that post, creating a session and data exposure risk inside WordPress administration workflows.
Executive priority
Treat this as a moderate-priority WordPress administration risk. It is not described as unauthenticated or actively exploited, but public exploit information and stored XSS can affect privileged users who preview content.
Technical view
This is a persistent cross-site scripting issue in Soliloquy Lite 2.5.6. The source bundle says script tags placed in the post_title parameter are stored and executed during post preview. It is CVSS 5.4 with low privileges required and user interaction required.
Likely exposure
Exposure is limited to WordPress sites running Soliloquy Lite 2.5.6 where an attacker has authenticated access capable of editing affected content. Public internet exposure alone is not enough based on the provided sources.
Exploitation context
The bundle cites an ExploitDB entry, indicating public exploit information exists. CISA KEV is false in the bundle, and no source provided here states active exploitation in the wild.
Researcher notes
Evidence supports authenticated persistent XSS against Soliloquy Lite 2.5.6. The provided sources do not identify a patched version, affected version range beyond 2.5.6, or confirmed exploitation, so remediation should be tied to vendor and WordPress plugin guidance.
Mitigation direction
Inventory WordPress sites for Soliloquy Lite version 2.5.6.
Check vendor and WordPress plugin guidance for a fixed release or removal advice.
Disable Soliloquy Lite 2.5.6 if business impact is acceptable.
Restrict WordPress editing privileges to trusted users only.
Review stored content for unexpected script tags in titles.
Validation and detection
Confirm whether Soliloquy Lite 2.5.6 is installed and active.
Review WordPress users with content editing permissions.
Audit recent post or slider title changes by authenticated users.
Check previewed content paths for stored script execution evidence.
Verify remediation against vendor or WordPress plugin guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.