Cost CalculatorWordPress extension · Bold Themes
CVE-2021-24820
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 · uneditedThe Cost Calculator WordPress plugin through 1.6 allows authenticated users (Contributor+ in versions < 1.5, and Admin+ in versions <= 1.6) to perform path traversal and local PHP file inclusion on Windows Web Servers via the Cost Calculator post's Layout
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 confidenceThe Cost Calculator WordPress plugin through version 1.6 contains a path traversal vulnerability allowing authenticated users (Contributor+ in older versions, Admin+ in v1.5-1.6) to perform local PHP file inclusion via the Cost Calculator post's Layout parameter on Windows Web Servers. This could allow attackers to execute arbitrary PHP code by including malicious local files.
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
Cost CalculatorWordPress extension
<= 1.6CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Cost Calculator plugin is installedNavigate to WordPress admin > Plugins and look for 'Bold Themes Cost Calculator' in the installed plugins listAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin > Plugins, find the Bold Themes Cost Calculator plugin and note the version number displayedAffected if The installed version is 1.6 or any version lower than the latest patched version
-
Confirm server operating systemCheck the web server OS - this can be done via hosting control panel, server info, or by running 'systeminfo' on Windows or 'uname -a' on Linux via SSHAffected if The web server is running Windows (the vulnerability specifically affects Windows Web Servers)
-
Identify Layout parameter usageCheck Cost Calculator post types for any configured 'Layout' settings or parameters - inspect page source or use browser dev tools to identify if 'layout' parameter is being passed in requestsAffected if The Layout parameter is configurable and accessible to authenticated users (Contributor+ or Admin+ depending on version)
The environment is affected if the Bold Themes Cost Calculator plugin (version 1.6 or lower) is installed on a Windows web server and the Layout parameter feature is accessible to authenticated users.
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 the Cost Calculator plugin to the latest version which includes proper input validation and sanitization of the Layout parameter to prevent path traversal sequences. Restrict contributor-level user permissions until the patch is applied.
Fix this in Cost Calculator
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-2021-24820 — 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-2021-24820 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