Security readout for executives and security teams
Plain-English summary
CVE-2025-22343 affects the WordPress wpSOL plugin through version 1.2.0. A malicious site could trick an authenticated WordPress user into making a change that stores attacker-controlled script in the site. That script may later run in a visitor or administrator browser, creating confidentiality, integrity, and availability risk.
Executive priority
Prioritize sites running wpSOL because stored XSS can affect administrators and visitors. Treat this as high risk, but do not assume active exploitation from the provided evidence.
Technical view
The issue is a CSRF vulnerability leading to stored XSS in koter84 wpSOL/wpsol through 1.2.0. The CVSS 3.1 score is 7.1: network reachable, low complexity, no attacker privileges, required user interaction, changed scope, and low C/I/A impact. Sources do not name a fixed version or detailed vulnerable endpoint.
Likely exposure
Exposure is limited to WordPress installations using the wpSOL/wpsol plugin at version 1.2.0 or earlier. Sites without this plugin are not indicated as affected by the supplied sources.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. The likely attack condition is social engineering: an attacker must cause an authenticated WordPress user to trigger a forged request that stores XSS.
Researcher notes
The public bundle identifies CWE-352 and stored XSS impact but lacks endpoint, proof-of-concept, patch, or exploitation details. Avoid assuming exploitability beyond the CVSS vector and Patchstack/CVE descriptions.
Mitigation direction
- Inventory WordPress sites for the wpSOL/wpsol plugin and record versions.
- Remove or disable wpSOL where it is not business-critical.
- Check vendor and Patchstack guidance for a fixed version or official mitigation.
- Restrict administrative access and reinforce CSRF-safe workflows for privileged users.
Validation and detection
- Confirm whether wpSOL/wpsol is installed on each WordPress site.
- Verify installed wpSOL versions are greater than 1.2.0 if a fixed release exists.
- Review vendor and Patchstack records for updated remediation guidance.
- Inspect wpSOL-managed settings or content for unexpected stored script content.
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-22343 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/wpsol/vulnerability/wordpress-wpsol-plugin-1-2-0-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.