Dashboard To Do ListWordPress extension · Arwebdesign
CVE-2024-35723
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 · uneditedMissing Authorization vulnerability in Andrew Dashboard To-Do List dashboard-to-do-list.This issue affects Dashboard To-Do List: from n/a through <= 1.2.0.
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 confidenceMissing Authorization vulnerability in the Dashboard To-Do List WordPress plugin (versions <=1.2.0) allows attackers to perform actions or access functionality without proper permission checks, likely enabling unauthorized CRUD operations on to-do list data.
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
Dashboard To Do ListWordPress extension
< 1.3.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Locate the Dashboard To-Do List pluginCheck your WordPress installation's /wp-content/plugins/ directory for a folder named 'dashboard-to-do-list' or similar, or use WP-CLI: wp plugin list --name='dashboard-to-do-list'Affected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin file (usually dashboard-to-do-list.php) and locate the version comment/header, or run: wp plugin get dashboard-to-do-list --field=versionAffected if The version returned is 1.2.0 or lower (any version below 1.3.0)
-
Verify the plugin is activeCheck if the plugin is enabled in WordPress admin under Plugins > Installed Plugins, or run: wp plugin is-active dashboard-to-do-listAffected if The plugin is active and running on the site
If the Arwebdesign Dashboard To-Do List plugin is installed, active, and running version 1.2.0 or lower, the site is affected by this missing authorization vulnerability.
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.
dbcve · scoped1.3.0
Update Dashboard To-Do List to the latest patched version (likely 1.2.1 or higher). If no patched version is available, disable the plugin until a fix is released.
1.3.0
- Backup your WordPress site database and files before making any changes
- Navigate to the WordPress admin dashboard > Plugins
- Locate 'Dashboard To-Do List' in the installed plugins list
- Click 'Update now' to upgrade to version 1.3.0 or later
- Alternatively, use WP-CLI: wp plugin update dashboard-to-do-list
- Verify the plugin version shows 1.3.0 or higher after updating
- Test that the to-do list functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Dashboard To Do List
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35723 — 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-35723 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