Security readout for executives and security teams
Plain-English summary
CVE-2025-22520 affects the WordPress Tock Widget plugin through version 1.1. A malicious site could potentially cause a user’s browser to perform an unwanted action that results in stored cross-site scripting. This can affect site integrity and visitor trust, but the provided sources do not show active exploitation.
Executive priority
Treat as a high-priority WordPress plugin exposure if Tock Widget is deployed. Prioritize inventory first, because impact depends on plugin presence. If present, reduce exposure quickly while waiting for verified vendor or Patchstack remediation details.
Technical view
The CVE describes a CSRF weakness in Tock Widget that can lead to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope. The affected range is described as Tock Widget through <= 1.1.
Likely exposure
Exposure is likely limited to WordPress sites with the Tock Widget plugin installed, especially versions through 1.1. The source bundle does not identify affected hosting platforms, themes, or downstream products beyond this plugin.
Exploitation context
The CVE is not listed as KEV in the provided bundle. Exploitation would require user interaction consistent with CSRF, and successful abuse could store script content for later execution. No cited source in the bundle confirms public exploitation or weaponized exploit availability.
Researcher notes
Evidence is limited to the CVE description and Patchstack reference. The affected data has some ambiguity, but the human-readable description clearly states Tock Widget through <= 1.1. Avoid assuming a patched version unless vendor or Patchstack guidance confirms one.
Mitigation direction
- Inventory WordPress sites for the Tock Widget plugin and installed version.
- Check Patchstack and vendor guidance for a confirmed fixed release or official mitigation.
- Disable or remove the plugin where business impact permits until guidance is confirmed.
- Review stored widget content for unexpected or unauthorized changes.
- Ensure WordPress administrative sessions use strong access controls and least privilege.
Validation and detection
- Confirm whether each WordPress site has Tock Widget installed.
- Record plugin version and compare against the <= 1.1 affected range.
- Review security logs for suspicious widget configuration or content changes.
- Test remediation in staging before production plugin changes.
- Re-scan after mitigation to confirm the vulnerable plugin is absent or updated.
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-22520 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/tock-widget/vulnerability/wordpress-tock-widget-plugin-1-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.