dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-0952

HIGH · 8.1 CVSS v3.1 Published 2025-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 Eco Nature - Environment & Ecology WordPress Theme theme for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the 'cmsmasters_hide_admin_notice' AJAX action in all versions up to, and including, 2.0.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update option values to 'hide' on the WordPress site. This can be leveraged to update an option that would create an error on the site and deny service to legitimate users or be used to set some values to true such as registration.

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 Eco Nature WordPress theme has a broken access control vulnerability in the 'cmsmasters_hide_admin_notice' AJAX action, which lacks proper capability verification. This allows any authenticated user with Subscriber-level access or higher to directly modify WordPress options via AJAX, potentially causing denial of service by setting invalid option values or enabling unauthorized features like user registration.

MitigationUpgrade to version 2.0.5 or later where the capability check has been implemented. Alternatively, add proper capability verification (e.g., current_user_can('manage_options')) and nonce validation to the affected AJAX handler.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Identify Eco Nature theme installation and version
    Navigate to Appearance > Themes in WordPress admin panel and check if the Eco Nature theme is active. Note the installed version number from the theme details.
    Affected if Eco Nature theme is active and version is below 2.0.5 (the version with the fix)
  2. Locate the AJAX handler file
    Access your WordPress site files via FTP or file manager. Search for files containing 'cmsmasters_hide_admin_notice' - typically in the theme's functions.php or includes/ajax.php
    Affected if The cmsmasters_hide_admin_notice AJAX handler is found in the theme files
  3. Verify capability check is missing
    Open the file containing the cmsmasters_hide_admin_notice handler. Search for 'add_action' registering this AJAX action. Inspect the callback function for a capability check like 'current_user_can' or 'manage_options'.
    Affected if The AJAX handler callback function does NOT contain a capability check (e.g., current_user_can('manage_options')) before processing the request
  4. Test subscriber-level access to AJAX endpoint
    Log in with a user who has Subscriber role (lowest privilege). Use a tool like curl or Burp to send a POST request to /wp-admin/admin-ajax.php with action=cmsmasters_hide_admin_notice and arbitrary option data (e.g., option_name and option_value parameters).
    Affected if The AJAX request executes successfully and modifies WordPress options without returning a permission denied error

If Eco Nature theme below version 2.0.5 is active AND the cmsmasters_hide_admin_notice AJAX handler lacks capability verification, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.0.5 or later where the capability check has been implemented. Alternatively, add proper capability verification (e.g., current_user_can('manage_options')) and nonce validation to the affected AJAX handler.

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-2025-0952 — 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-2025-0952 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