Yoast Duplicate-Post WordPress Plugin 3.2.3 contains a persistent cross-site scripting vulnerability in plugin settings parameters. Attackers can inject malicious scripts into title prefix, suffix, menu order, and blacklist fields to execute arbitrary JavaScript in admin interfaces.
Security readout for executives and security teams
Plain-English summary
This is a stored cross-site scripting issue in the Yoast Duplicate Post WordPress plugin. A highly privileged user could save malicious script content in plugin settings, causing JavaScript to run later in admin interfaces. The bundle does not show active exploitation, but it does include a public exploit reference.
Executive priority
Treat as a moderate WordPress hygiene issue, not an emergency based on the provided evidence. Prioritize sites where administrator accounts are shared, weakly protected, or externally managed, because exploitation depends on high-privilege settings access.
Technical view
The described flaw affects Duplicate-Post 3.2.3 settings parameters including title prefix, suffix, menu order, and blacklist fields. It requires high privileges and can persist arbitrary JavaScript into admin-facing pages. CVSS 3.1 is 5.5 with changed scope, low confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running the vulnerable Yoast Duplicate Post/Duplicate-Post plugin version and allowing high-privilege users to change plugin settings. Public internet exposure matters less than admin account security and plugin version hygiene.
Exploitation context
The source bundle includes an ExploitDB reference, but KEV is false and no cited source states active exploitation. The privilege requirement is high, so compromise risk is mainly from malicious, compromised, or misused administrator-level accounts.
Researcher notes
There is a version inconsistency in the bundle: the title and description name 3.2.3, while the affected entry lists 0.3. Validate against CVE, VulnCheck, Wordfence, and vendor data before asserting precise affected ranges or fixed versions.
Mitigation direction
Check Yoast or WordPress plugin guidance for the fixed supported version.
Update or remove the plugin according to vendor guidance.
Restrict administrator-level WordPress access to trusted users only.
Review plugin settings for unexpected script-like content.
Monitor WordPress admin activity for unauthorized settings changes.
Validation and detection
Inventory WordPress sites using Yoast Duplicate Post or Duplicate-Post.
Compare installed plugin versions against vendor and advisory information.
Review affected settings fields for suspicious stored content.
Confirm only trusted administrators can modify plugin settings.
Check security tools for detections tied to this plugin advisory.
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.
cve · low confidence lookup
CVE-2019-25314 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.