Total UpkeepWordPress extension · Boldgrid
CVE-2024-24869
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in BoldGrid Total Upkeep allows Relative Path Traversal.This issue affects Total Upkeep: from n/a through 1.15.8.
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 confidencePath traversal vulnerability in BoldGrid Total Upkeep plugin allows attackers to escape the intended directory restrictions and access sensitive files outside the web root through specially crafted relative path sequences (e.g., ../../../'). The CVSS 7.5 indicates unauthenticated remote exploitation potential for confidential file disclosure.
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
< 1.15.9CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 BoldGrid Total Upkeep is installedCheck your WordPress plugins directory or wp-admin plugins list for 'Boldgrid Total Upkeep' or 'total-upkeep'. Look for the plugin folder in /wp-content/plugins/Affected if The plugin is present on the system
-
Determine the installed version of BoldGrid Total UpkeepCheck the plugin header in the main PHP file (usually total-upkeep.php or class-boldgrid-total-upkeep.php) for the 'Version' field, or view it in WordPress admin under Plugins > Installed PluginsAffected if The version number is less than 1.15.9 (e.g., 1.15.8, 1.14.0, etc.)
-
Verify if backup/restore functionality is accessibleCheck if the plugin's backup and restore endpoints are exposed and accessible without authentication. Look for URLs containing '/wp-json/total-upkeep/' or similar API paths used by the pluginAffected if The backup/restore endpoints are publicly accessible without login requirements
-
Review web server logs for path traversal attemptsExamine web server access logs for requests to the plugin that contain sequences like '../', '..%2F', or URL-encoded traversal patterns targeting the backup functionalityAffected if Logs show attempted directory traversal patterns (../../../) directed at the plugin
You are affected if BoldGrid Total Upkeep is installed with a version lower than 1.15.9 and the backup/restore functionality is accessible.
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.15.9
Upgrade Total Upkeep to version 1.15.9 or later. If no patch is available, implement web server-level restrictions to prevent directory traversal and audit the plugin's file handling functions for proper path validation.
Total Upkeep version 1.15.9
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find BoldGrid Total Upkeep in the plugin list
- Check if current version is below 1.15.9
- If vulnerable, click 'Update Now' or manually update to version 1.15.9 or later
- Verify the update was successful by confirming the new version number
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
- 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-24869 — 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-24869 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