dbcve.org
Total UpkeepWordPress extension · Boldgrid

CVE-2024-9461

HIGH · 7.2 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 1.16.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.16.6 via the cron_interval parameter. This is due to missing input validation and sanitization. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute code on the server.

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 · high confidence

The Total Upkeep WordPress backup plugin fails to validate and sanitize the cron_interval parameter, allowing authenticated administrators to inject and execute arbitrary server-side code through this unchecked input field.

MitigationUpdate the Total Upkeep plugin to version 1.16.7 or later which addresses the input validation vulnerability in the cron_interval parameter.

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
Total UpkeepWordPress extension
Affected:< 1.16.7

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Total Upkeep plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Boldgrid Total Upkeep' or 'Total Upkeep' in the installed plugins list
    Affected if The plugin is not present in the plugins list
  2. Check the installed version number
    In WordPress admin > Plugins, click on the Total Upkeep plugin to view its details, or check the plugin files in /wp-content/plugins/ for a version indicator in the main PHP file
    Affected if The displayed version number is less than 1.16.7 (for example, 1.16.6, 1.15.x, etc.)
  3. Verify cron scheduling is configured
    Check WordPress cron settings or Total Upkeep scheduling settings. Look for any scheduled backup tasks that use the cron_interval parameter in the plugin configuration
    Affected if Cron-based scheduling is enabled and the cron_interval parameter can be modified through the plugin settings accessible to administrators

You are affected if Boldgrid Total Upkeep is installed with a version lower than 1.16.7 and the plugin's cron scheduling with the cron_interval parameter is accessible to authenticated administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.16.7 or later
Fixed in 1.16.7
Interim mitigation

Update the Total Upkeep plugin to version 1.16.7 or later which addresses the input validation vulnerability in the cron_interval parameter.

Recommended fix High confidence

Total Upkeep version 1.16.7 or later

  1. 1. Create a full backup of the WordPress site including database and files
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Locate the Total Upkeep plugin (Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid)
  4. 4. Click Update Now or go to Plugins > Add New > Upload if auto-update is not available
  5. 5. Update to version 1.16.7 or later
  6. 6. Verify the plugin version reflects 1.16.7 or higher after update
  7. 7. Test that backup/restore functionality continues to work properly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Total Upkeep Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9461 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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