dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32546

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in StellarWP Restrict Content restrict-content allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Restrict Content: from n/a through <= 3.2.22.

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

Missing Authorization vulnerability in StellarWP Restrict Content plugin allows attackers to bypass access control restrictions due to incorrectly configured security levels, potentially enabling unauthorized access to restricted content functionality.

MitigationUpdate Restrict Content plugin to the latest version to obtain the security patch; alternatively, implement additional access control measures at the server or application level until the patch is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if StellarWP Restrict Content plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins directory for the 'restrict-content' or 'stellarwp-restrict-content' folder
    Affected if The plugin folder exists and the plugin is active on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, locate the Restrict Content plugin and note the version number displayed under the plugin name
    Affected if The installed version matches or falls within an affected version range (compare to any officially released patch versions)
  3. Verify if REST API endpoints are accessible without authentication
    Use a tool like curl or a browser to send a request to the site's /wp-json/restrict-content/v1/ endpoint (or similar API routes) without providing authentication credentials
    Affected if The API returns restricted content or sensitive data without requiring login or proper capability checks
  4. Inspect access control configuration settings
    Navigate to Restrict Content settings in WordPress admin (Settings > Restrict Content) and examine security level settings, role restrictions, and content protection configurations
    Affected if Security levels are set incorrectly, allowing lower-privileged users or unauthenticated users to access protected content
  5. Review server access logs for unauthorized access patterns
    Examine web server logs (Apache/Nginx) and WordPress debug logs for repeated requests to restricted content endpoints from unfamiliar IP addresses or unauthenticated user agents
    Affected if Logs show successful access to restricted content from users lacking appropriate permissions

A site is affected if it runs the StellarWP Restrict Content plugin and allows unauthenticated or under-privileged access to restricted content functionality via API or misconfigured security 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 Restrict Content plugin to the latest version to obtain the security patch; alternatively, implement additional access control measures at the server or application level until the patch is available.

Recommended fix Moderate confidence

Latest available version of Restrict Content plugin (version > 3.2.22)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Restrict Content' plugin by StellarWP
  4. 4. Check the current installed version (should be <= 3.2.22)
  5. 5. Click 'Update Now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. 6. After updating, verify the new version is installed (should be > 3.2.22)
  7. 7. Test that the restrict content functionality still works correctly for authorized users

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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