dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-4787

MEDIUM · 5.8 CVSS v3.1 Published 2024-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Cost Calculator Builder PRO for WordPress is vulnerable to arbitrary email sending vulnerability in versions up to, and including, 3.1.75. This is due to insufficient limitations on the email recipient and the content in the 'send_pdf' and the 'send_pdf_front' functions which are reachable via AJAX. This makes it possible for unauthenticated attackers to send emails with any content to any recipient.

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 Cost Calculator Builder PRO WordPress plugin fails to enforce authorization and input validation on the 'send_pdf' and 'send_pdf_front' AJAX endpoints. Unauthenticated attackers can abuse these endpoints to send arbitrary emails with controlled content to any recipient, effectively turning the site into an open email relay.

MitigationUpdate the Cost Calculator Builder PRO plugin to a version newer than 3.1.75 which should implement proper authentication checks, nonce verification, and email recipient/content validation on the affected AJAX handlers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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 checks

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

  1. Verify Cost Calculator Builder PRO plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cost Calculator Builder PRO' in the list. Note the installed version displayed.
    Affected if The plugin appears in the installed plugins list with a version number at or below 3.1.75
  2. Check WordPress plugins directory for the plugin files
    Access the WordPress filesystem via FTP, SSH, or hosting file manager. Navigate to /wp-content/plugins/ and look for a directory named 'cost-calculator-builder-pro' or similar. Open the main plugin file (usually cost-calculator-builder.php or similar) to read the version header comment.
    Affected if The plugin directory exists and the version header in the main PHP file shows a version at or below 3.1.75
  3. Test AJAX endpoint accessibility (send_pdf)
    Send a crafted POST request to your site's /wp-admin/admin-ajax.php endpoint with action=ccb_send_pdf. Inspect whether the server returns a 200 OK response rather than a 401 Unauthorized or 403 Forbidden error. Example: curl -X POST https://yourdomain.com/wp-admin/admin-ajax.php -d 'action=ccb_send_pdf'
    Affected if The endpoint responds without requiring authentication (no 401/403 error, or returns a JSON error that indicates missing nonce rather than missing auth)
  4. Test AJAX endpoint accessibility (send_pdf_front)
    Send a crafted POST request to your site's /wp-admin/admin-ajax.php endpoint with action=ccb_send_pdf_front. Check if the server accepts the request without authentication. Example: curl -X POST https://yourdomain.com/wp-admin/admin-ajax.php -d 'action=ccb_send_pdf_front'
    Affected if The endpoint responds without requiring authentication (no 401/403 error, or returns a JSON error indicating missing nonce rather than blocked access)
  5. Review server access logs for recent AJAX requests
    Check your web server access logs (Apache/Nginx) for entries containing 'admin-ajax.php' with actions 'ccb_send_pdf' or 'ccb_send_pdf_front' from unauthenticated IPs. Look for POST requests without valid WordPress nonces in the query string.
    Affected if Logs show unauthenticated POST requests to these endpoints (IP not logged into WordPress, missing nonce parameter)

Your environment is affected if the Cost Calculator Builder PRO plugin version is 3.1.75 or lower AND the AJAX endpoints /wp-admin/admin-ajax.php are accessible without authentication for the ccb_send_pdf or ccb_send_pdf_front actions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Cost Calculator Builder PRO plugin to a version newer than 3.1.75 which should implement proper authentication checks, nonce verification, and email recipient/content validation on the affected AJAX handlers.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4787 — 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-4787 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