The WordPress Comments Import & Export plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save_settings function in all versions up to, and including, 2.4.3. Additionally, the plugin fails to properly sanitize and escape FTP settings parameters.
This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts on the plugin settings page that will execute whenever an administrative user accesses an injected page.
The vulnerability was partially fixed in version 2.4.3 and fully fixed in version 2.4.4
Security readout for executives and security teams
Plain-English summary
A logged-in WordPress user with even Subscriber access can place malicious script in vulnerable plugin settings. The script runs when an administrator opens the affected page, potentially exposing information or enabling unauthorized actions in the administrator’s browser context. Versions through 2.4.3 are affected; 2.4.4 fully fixes the issue.
Executive priority
Schedule prompt remediation rather than emergency shutdown. Prioritize internet-facing sites permitting subscriber registration or containing untrusted accounts. Although rated medium and unsupported by evidence of active exploitation, successful abuse places administrators in the execution path and can affect confidentiality and integrity.
Technical view
The save_settings function lacks an adequate capability check, allowing low-privileged authenticated users to modify data. FTP setting parameters are also insufficiently sanitized and escaped, creating stored cross-site scripting. The source reports a partial fix in 2.4.3 and a complete fix in 2.4.4. CVSS 3.1 is 6.4, with confidentiality and integrity impact but no stated availability impact.
Likely exposure
Exposure exists where the Comments Import & Export plugin version 2.4.3 or earlier is active and untrusted users can obtain Subscriber-level accounts. Sites with public registration, numerous low-privileged users, or shared administration are more likely to present a practical attack path.
Exploitation context
Exploitation requires an authenticated Subscriber-level or higher account. Injected script executes when an administrator accesses the affected plugin page. The bundle does not identify public exploitation, and CVE-2025-3919 is not listed as a KEV in the supplied data.
Researcher notes
The supplied affected-product structure contains a generic version value of "0," while the narrative explicitly identifies versions through 2.4.3. Validation should therefore use the narrative and vendor changesets, confirming 2.4.4 or later. The sources establish missing authorization and stored XSS but do not document observed attacks or broader impacts.
Mitigation direction
Update Comments Import & Export to version 2.4.4 or later.
Confirm the installed release is not the partially fixed version 2.4.3.
Temporarily disable the plugin if updating cannot be completed promptly.
Review low-privileged accounts and remove access that is no longer required.
Validation and detection
Inventory WordPress sites for the Comments Import & Export plugin.
Verify each active installation reports version 2.4.4 or later.
Inspect saved FTP settings for unexpected or script-like content.
Review administrative activity around the plugin settings page.
Confirm low-privileged users cannot invoke settings changes after updating.
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.