Security readout for executives and security teams
Plain-English summary
A WordPress plugin used for cPanel integration can be abused through CSRF to plant stored cross-site scripting. A successful attack needs user interaction, but could affect confidentiality, integrity, and availability at low impact levels. Public sources identify versions through 1.4.6 as affected.
Executive priority
Treat as high priority for WordPress environments using this plugin. Prioritize discovery first because exposure depends on plugin presence. If found, reduce risk by updating, disabling, or following vendor guidance.
Technical view
CVE-2025-22690 is a CWE-352 CSRF issue in DigiTimber cPanel Integration for WordPress that can lead to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, required user interaction, and changed scope.
Likely exposure
Exposure is limited to WordPress sites running DigiTimber cPanel Integration, package digitimber-cpanel-integration, through version 1.4.6. The source bundle provides no CPEs and no evidence of other affected products.
Exploitation context
The bundle marks KEV false and provides no cited evidence of active exploitation. The CVSS vector indicates an attacker needs user interaction, consistent with CSRF-to-stored-XSS risk rather than unauthenticated direct compromise.
Researcher notes
Evidence is limited to the CVE description, CVSS data, and Patchstack reference. No public source in the bundle names a patch version, exploit activity, or detailed technical root cause beyond CSRF leading to stored XSS.
Mitigation direction
Inventory WordPress sites for DigiTimber cPanel Integration installations.
If installed version is 1.4.6 or earlier, check vendor or Patchstack guidance immediately.
Update to a fixed version if one is available from the vendor.
Disable or remove the plugin where it is not operationally required.
Review administrative access and enforce strong session and CSRF protections site-wide.
Validation and detection
Confirm plugin presence and version across managed WordPress environments.
Check whether Patchstack or vendor guidance names a fixed release.
Review WordPress content and plugin-managed settings for unexpected injected script content.
Verify monitoring covers WordPress admin changes and unusual stored-content modifications.
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-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.
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.