CVE-2024-12848
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 SKT Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to a missing capability check on the 'addLibraryByArchive' function in all versions up to, and including, 4.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files that make remote code execution possible.
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 SKT Page Builder WordPress plugin lacks a capability check on the addLibraryByArchive function, allowing any authenticated user with subscriber-level permissions to upload arbitrary files. This enables remote code execution by uploading malicious PHP files.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed SKT Page Builder versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'SKT Page Builder', and note the version number displayedAffected if Version is lower than 4.7 (or version cannot be determined and plugin is active)
-
Confirm plugin is activeCheck if SKT Page Builder is currently enabled in the Plugins list (look for 'Active' status)Affected if Plugin is active and version is below 4.7 or unknown
-
Verify if subscriber-level users existGo to Users > All Users and check for any users assigned the 'Subscriber' role or any role below Editor levelAffected if Any authenticated user with subscriber-level or higher access exists in the system
-
Check for unauthorized uploadsInspect the wp-content/uploads/skt-builder/ directory (or similar upload directories) for unexpected .php files with suspicious names or recent timestampsAffected if Unexpected PHP files are present in upload directories
User is affected if SKT Page Builder plugin is active, version is below 4.7 (or unconfirmed), and any subscriber-level or higher user account exists on the WordPress site.
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 · scopedUpdate the plugin to version 4.7 or later which includes proper capability validation. Until patched, restrict file upload capabilities or disable the plugin.
Version 4.7 or latest available version (any version above 4.6)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find SKT Page Builder in the plugin list
- Check if current version is 4.6 or below
- If vulnerable, click 'Update Now' to update to the latest version (4.7 or higher)
- Alternatively, download the latest version from wordpress.org/plugins/skt-page-builder/ and upload via Plugins > Add New > Upload Plugin
- Verify the update was successful and the new version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12848 — 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-12848 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