Custom Dashboard WidgetsWordPress extension · Custom Dashboard Widgets Project
CVE-2024-22290
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 AboZain,O7abeeb,UnitOne Custom Dashboard Widgets allows Cross-Site Scripting (XSS).This issue affects Custom Dashboard Widgets: from n/a through 1.3.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Custom Dashboard Widgets allows authenticated attackers to inject malicious scripts via XSS. Attackers can trick administrators into submitting crafted requests that store XSS payloads in dashboard widgets, potentially leading to session hijacking or defacement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Custom Dashboard WidgetsWordPress extension
<= 1.3.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 if Custom Dashboard Widgets plugin is installedCheck your WordPress or CMS plugin directory for the 'Custom Dashboard Widgets' plugin. Common paths include /wp-content/plugins/ or equivalent. Look for plugin files or check the plugins admin panel.Affected if The plugin is found in the system
-
Determine the installed version of Custom Dashboard WidgetsOpen the main plugin file (usually named plugin.php or similar in the Custom Dashboard Widgets directory) and locate the version declaration in the plugin header comment. Compare against the affected range: <= 1.3.1Affected if The installed version is 1.3.1 or lower
-
Inspect widget configuration actions for CSRF protectionExamine the PHP files handling widget configuration (such as widget save, update, or create functions). Look for nonce verification or token validation calls before processing any widget settings. Check if admin POST/GET requests that modify widgets include anti-CSRF token checks.Affected if No nonce verification or anti-CSRF token validation is found in widget configuration handlers
-
Check widget content rendering for XSS sanitizationReview the code that outputs or displays dashboard widget content. Look for functions that sanitize output such as esc_html(), esc_attr(), or similar XSS prevention functions before rendering user-supplied widget data.Affected if Widget content is rendered without sanitization functions, or sanitization is missing entirely
You are affected if the Custom Dashboard Widgets plugin version 1.3.1 or lower is installed AND widget configuration lacks CSRF protection AND widget content is not sanitized before rendering.
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 dataUpdate to the latest version of Custom Dashboard Widgets when available; implement anti-CSRF tokens for all widget configuration actions and sanitize all user-supplied widget content before rendering.
Fix this in Custom Dashboard Widgets
Scoped from the published advisory
- 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-2024-22290 — 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-2024-22290 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