CVE-2025-22690
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in DigiTimber DigiTimber cPanel Integration digitimber-cpanel-integration allows Stored XSS.This issue affects DigiTimber cPanel Integration: from n/a through <= 1.4.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in DigiTimber cPanel Integration (versions <= 1.4.6) allows attackers to craft malicious requests that result in Stored XSS. Attackers can trick authenticated users into submitting requests that inject persistent malicious scripts into the application, which then execute when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify DigiTimber cPanel Integration installationLocate the DigiTimber plugin/module in your cPanel environment. Check cPanel addon directories (commonly /var/cpanel/cpanel/addons/ or /usr/local/cpanel/whostmgr/docroot/cgi/), the web interface plugin list, or any standalone DigiTimber installation files.Affected if DigiTimber cPanel Integration is present in the environment
-
Determine installed versionFind the version number in the plugin files (often in a config file, version.php, or addon metadata), the cPanel addon management interface, or any bundled version information file. Compare your version to the affected range.Affected if Installed version is 1.4.6 or lower
-
Verify CSRF protection on state-changing operationsInspect the forms and API endpoints in the DigiTimber cPanel Integration for anti-CSRF tokens. Check if state-changing operations (creating/modifying content) include and validate CSRF tokens in their requests.Affected if State-changing operations lack anti-CSRF token validation and the application allows unsanitized input to be stored
Environment is affected if DigiTimber cPanel Integration version 1.4.6 or lower is installed and the application does not implement anti-CSRF tokens on state-changing operations, allowing Stored XSS injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens for all state-changing operations and apply proper input validation with output encoding to prevent Stored XSS. Update to a patched version if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22690 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data