dbcve.org
Whmcs Client AreaWordPress extension · Whmpress

CVE-2024-9195

HIGH · 8.8 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to 4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 WHMPress - WHMCS Client Area plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the update_settings case in the /admin/ajax.php file in all versions up to, and including, 4.3-revision-3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 WHMPress WordPress plugin has a broken access control vulnerability in its AJAX handler. Due to a missing capability check on the update_settings function in admin/ajax.php, any authenticated user with Subscriber-level access or higher can modify arbitrary WordPress options. Attackers exploit this by enabling user registration and setting the default new user role to Administrator, allowing them to self-register administrative accounts and fully compromise the site.

MitigationUpdate the plugin if a patched version is available; otherwise remove the plugin entirely or implement a custom code-level fix that adds proper capability checks (manage_options) to the update_settings AJAX action. Consider replacing with an alternative solution as the plugin may be abandoned.

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
Whmcs Client AreaWordPress extension
Affected:< 4.3= 4.3

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WHMPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WHMPress' or 'Whmpress Whmcs Client Area'. Alternatively, check the /wp-content/plugins/ directory for a whmpress folder.
    Affected if WHMPress plugin is present on the WordPress site
  2. Check installed WHMPress version
    In WordPress admin Plugins page, find WHMPress and view the version number. Or check the plugin's main PHP file header in /wp-content/plugins/whmpress/ for the Version tag.
    Affected if Version is 4.3 or any version lower than 4.3-revision-3 (e.g., 4.2.x, 4.1.x, etc.)
  3. Confirm vulnerable ajax endpoint exists
    Check if the file /wp-content/plugins/whmpress/admin/ajax.php exists on the server. This is the file containing the vulnerable update_settings function.
    Affected if The file /admin/ajax.php exists within the WHMPress plugin directory
  4. Review user role configuration
    In WordPress admin, go to Settings > General and check the 'Default Role' setting. Also verify if 'Anyone can register' is enabled under General Settings.
    Affected if The default user role is set to Administrator, or user registration is enabled and was not intentionally configured by an administrator

A WordPress site with WHMPress plugin versions 4.3 or below installed is affected if the plugin is active and any subscriber-level user account exists on the site.

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
Upgrade available Upgrade to 4.3 or later
Fixed in 4.3
Interim mitigation

Update the plugin if a patched version is available; otherwise remove the plugin entirely or implement a custom code-level fix that adds proper capability checks (manage_options) to the update_settings AJAX action. Consider replacing with an alternative solution as the plugin may be abandoned.

Recommended fix Moderate confidence

Latest version of WHMPress - WHMCS Client Area (version 4.4 or higher)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate the WHMPress - WHMCS Client Area plugin.
  4. 4. Check the current installed version to confirm it is 4.3-revision-3 or earlier.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. After updating, verify the new version number in the plugins list.
  7. 7. Test that the plugin functionality still works as expected.
  8. 8. Confirm that the update_settings ajax action now properly checks for administrator capabilities.
Caveat Minor: Verify plugin functionality after upgrade as any plugin update could affect site behavior

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

Fix this in Whmcs Client Area Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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