CVE-2024-13856
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 Your Friendly Drag and Drop Page Builder — Make Builder plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.1.10 via the make_builder_ajax_subscribe() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 Make Builder plugin for WordPress contains an SSRF vulnerability in the make_builder_ajax_subscribe() function. Authenticated users with Subscriber-level access can supply arbitrary URLs that the server will request, potentially reaching internal services, cloud metadata endpoints, or other sensitive resources. The function lacks proper validation of user-supplied input used to determine the request target.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Make Builder plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'Make Builder' (or 'Make' theme builder component). Note the installed version number.Affected if The plugin is present with any version below the patched release.
-
Locate the vulnerable AJAX endpointSearch the plugin files for 'make_builder_ajax_subscribe' function or the AJAX action hook 'wp_ajax_make_builder_subscribe' or 'wp_ajax_nopriv_make_builder_subscribe'. Check if these exist in the plugin directory.Affected if The vulnerable function exists in the installed plugin version.
-
Confirm subscriber-level access is possibleCheck WordPress user roles: go to Users > All Users and verify if any users have the 'Subscriber' role. Also verify if the AJAX endpoint accepts requests from non-logged-in users (nopriv).Affected if Subscriber role users exist or the endpoint is accessible without authentication.
-
Check URL parameter handling in subscribe functionInspect the make_builder_ajax_subscribe function code to see if user-supplied URL parameters are validated against an allowlist or restricted to expected domains. Look for wp_remote_get or similar calls using unsanitized input.Affected if The function accepts arbitrary URLs without strict validation or allowlisting.
A user is affected if they have the Make Builder plugin installed with the vulnerable function present and subscriber-level (or unauthenticated) users can access the subscribe AJAX endpoint.
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 plugin to the latest version when available. Until then, restrict access to the affected AJAX endpoint using capability checks, implement strict allowlist validation for any URL parameters, and consider disabling the subscription functionality if not needed.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13856 — 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-13856 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