dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-4280

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 White Label CMS plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the reset_plugin function in all versions up to, and including, 2.7.3. This makes it possible for unauthenticated attackers to reset plugin settings.

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 White Label CMS WordPress plugin has a Broken Access Control vulnerability where the reset_plugin function lacks proper capability verification, allowing unauthenticated attackers to reset all plugin settings to default via a simple HTTP request.

MitigationUpdate the White Label CMS plugin to version 2.7.4 or later which contains the capability check fix. If an update is unavailable, disable the plugin or add interim access controls at the web server level.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Confirm White Label CMS plugin is installed
    Navigate to WordPress admin > Plugins and look for 'White Label CMS' in the installed plugins list
    Affected if The plugin does not appear in the installed plugins list, then you are not affected by this vulnerability
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find White Label CMS and note the version number displayed below the plugin name
    Affected if The installed version is less than 2.7.4, indicating the capability check fix has not been applied
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the White Label CMS plugin shows as 'Active'
    Affected if The plugin is active and the version is below 2.7.4, the vulnerable reset function is accessible
  4. Test for unauthenticated reset access (optional scan)
    Send a POST request to the site endpoint (typically /wp-admin/admin-post.php with action=reset_wlcms_settings) without providing authentication credentials and observe the response
    Affected if The request successfully resets plugin settings without returning an authentication error, the vulnerability is confirmed to be exploitable

You are affected if White Label CMS plugin version 2.7.4 or later is not installed and the plugin is active, allowing unauthenticated reset of plugin settings.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the White Label CMS plugin to version 2.7.4 or later which contains the capability check fix. If an update is unavailable, disable the plugin or add interim access controls at the web server level.

Recommended fix High confidence

Version 2.7.4 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the White Label CMS plugin
  4. Check if the current version is 2.7.3 or lower
  5. If vulnerable, click 'Update Now' to install version 2.7.4 or later
  6. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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