Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using the Elevio plugin through version 4.4.1. A malicious site could trick a user into triggering a change that stores script in the site, creating follow-on risk when that content is viewed.
Executive priority
Treat this as a high-priority WordPress plugin exposure where Elevio is deployed. Prioritize inventory and update decisions before broader remediation work, especially for externally managed or business-critical sites.
Technical view
The issue is a CSRF weakness that can lead to stored XSS in the Elevio WordPress plugin. CVSS 3.1 is 7.1 with network access, low complexity, no attacker privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress deployments with the Elevio plugin installed and enabled at version 4.4.1 or earlier. The source bundle does not identify affected configurations beyond the plugin/version range.
Exploitation context
The CVE is not listed as KEV in the supplied data. The CVSS vector requires user interaction, so risk is most credible through social engineering or unsafe browsing while an affected site user is active.
Researcher notes
Evidence identifies CSRF leading to stored XSS, but the bundle does not include vulnerable parameters, affected roles, proof of exploitation, or a named fixed version. Avoid assuming exploitability details beyond CVSS and the published description.
Mitigation direction
- Inventory WordPress sites for the Elevio plugin and version.
- Check vendor or Patchstack guidance for a fixed version or official mitigation.
- Update the plugin if a vendor-supported fixed release is available.
- Disable or remove the plugin if it is unused or no fix is available.
- Limit administrative browsing from active WordPress sessions where practical.
Validation and detection
- Confirm whether Elevio is installed and enabled on each WordPress site.
- Record the installed plugin version and compare it with 4.4.1 or earlier.
- Review vendor and Patchstack pages for updated remediation details.
- Check site content/settings for unexpected stored script or markup changes.
- Review recent administrative activity for suspicious cross-site request patterns.
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.
CWE-352: 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.
Open ATT&CK lookupCVE-2025-22328 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
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/elevio/vulnerability/wordpress-elevio-plugin-4-4-1-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.