CVE-2024-43247
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 · uneditedMissing Authorization vulnerability in creativeon WHMpress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WHMpress: from n/a through 6.2-revision-5.
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 confidenceMissing authorization vulnerability in creativeon WHMpress plugin allows unauthenticated or low-privileged users to access functionality that should be constrained by access control lists (ACLs). This is a broken access control issue where certain functions or pages lack proper permission checks, potentially enabling unauthorized actions.
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 if WHMpress plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named whmpress, whmpress-xt, or similar whmpress variantAffected if The WHMpress plugin directory exists in the WordPress installation
-
Determine installed WHMpress versionOpen the main plugin file (usually whmpress.php or readme.txt in the plugin folder) and locate the version declaration comment or the Version headerAffected if The version cannot be determined or is unknown (unable to verify if patched)
-
Inspect plugin for missing authorization checksReview the plugin source code in the includes/ or admin/ subdirectories for functions that handle sensitive operations (such as settings changes, data export, or user management) and verify they include current_user_can() or similar capability checks before executingAffected if Sensitive functions lack proper capability or permission verification before allowing actions
-
Test access to restricted functionalityWith a low-privileged user account (subscriber or contributor role) or unauthenticated, attempt to access known WHMpress admin pages or AJAX endpoints by navigating directly to their URLsAffected if Restricted admin pages or AJAX actions are accessible without proper authorization
The environment is affected if the WHMpress plugin is installed and sensitive functions or admin pages can be accessed by unauthenticated or low-privileged users without proper capability checks.
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 dataImplement proper authorization checks (e.g., capability/permission verification) on all sensitive functions and admin pages in WHMpress, ensuring that user roles and capabilities are validated before granting access to restricted functionality.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43247 — 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-43247 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