Sitebuilder Dynamic ComponentsWordPress extension · Brandonclark
CVE-2024-49625
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 · uneditedDeserialization of Untrusted Data vulnerability in sphoid SiteBuilder Dynamic Components sitebuilder-dynamic-components allows Object Injection.This issue affects SiteBuilder Dynamic Components: from n/a through <= 1.0.
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 confidenceThis is a PHP Object Injection vulnerability caused by insecure deserialization of untrusted data in sphoid SiteBuilder Dynamic Components. The flaw allows remote attackers to inject arbitrary PHP objects into the application by supplying malicious serialized payloads, potentially achieving remote code execution on the affected system.
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
Sitebuilder Dynamic ComponentsWordPress extension
<= 1.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SiteBuilder Dynamic Components installationSearch the web root directory for files related to 'sitebuilder', 'dynamic components', 'sphoid', or 'brandonclark'. Common paths include /wp-content/plugins/, /components/, or the main sitebuilder directory. Use: find /path/to/webroot -iname '*sitebuilder*' -o -iname '*sphoid*' 2>/dev/nullAffected if The component files are present on the server
-
Determine installed versionCheck for version information in component files, readme.txt, or configuration files within the SiteBuilder directory. Look for a 'version' variable or file containing version metadata. Compare against the affected range: <= 1.0Affected if The installed version is 1.0 or any version number less than or equal to 1.0
-
Identify deserialization entry pointsSearch the SiteBuilder component files for PHP functions that perform deserialization: unserialize(), var_dump(), var_export(), or similar. Check files in the 'dynamic-components' or 'components' subdirectory for these vulnerable function calls. Use: grep -r 'unserialize' /path/to/sitebuilder/Affected if The code contains unserialize() calls processing untrusted input without validation
-
Verify the component is web-accessibleConfirm the vulnerable component is exposed via HTTP by checking if the SiteBuilder directory is within the publicly accessible web root. Attempt to access the component directly via browser or curl to confirm it respondsAffected if The vulnerable component is reachable via HTTP/HTTPS requests from the internet or internal network
-
Check for exploitation indicatorsReview web server access logs and PHP error logs for patterns indicating PHP object injection attempts. Look for serialized PHP objects in request parameters, unusual object class names, or errors related to __wakeup, __destruct, or __toString methodsAffected if Log analysis reveals serialized payloads in requests or PHP object injection-related errors
The environment is affected if Brandonclark SiteBuilder Dynamic Components version 1.0 or lower is installed and the vulnerable deserialization code is accessible via web requests.
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 dataUpgrade to a patched version of SiteBuilder Dynamic Components. If no patched version is available, disable or remove the affected component and implement a Web Application Firewall (WAF) as an interim control until a fix is available.
Fix this in Sitebuilder Dynamic Components
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49625 — 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-49625 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