dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-35875

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-13
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
Missing Authorization vulnerability in Jegstudio Gutenverse allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Gutenverse: from n/a through 1.8.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 confidence

The Gutenverse WordPress plugin (versions through 1.8.5) has a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated or unauthorized users to access functionality that should require higher privileges.

MitigationUpdate Gutenverse to the latest version (1.8.6 or later) which should contain the authorization fix, and audit user roles/permissions after patching.

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. Check Gutenverse plugin installation status
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and locate Gutenverse in the list. Note the version number displayed below the plugin name.
    Affected if Gutenverse plugin is installed and version is 1.8.5 or earlier
  2. Verify plugin version via WP-CLI
    Run command: wp plugin list --name=gutenverse --format=table
    Affected if Version column shows 1.8.5 or lower
  3. Check plugin version file directly
    Access the Gutenverse plugin main file (wp-content/plugins/gutenverse/package.json or gutenverse.php) and read the Version field.
    Affected if Version string reads 1.8.5 or below
  4. Confirm WordPress user roles exist
    Navigate to WordPress admin > Users > Roles and Permissions, or use WP-CLI: wp role list
    Affected if Unexpected or unauthorized roles exist that should not have elevated access
  5. Test for unauthenticated access to Gutenverse endpoints
    Inspect network requests when using Gutenverse blocks; check if API endpoints under /wp-json/gutenverse/ are accessible without authentication by sending a request to those URLs without auth headers.
    Affected if API endpoints return expected data without requiring login credentials

The environment is affected if Gutenverse plugin version is 1.8.5 or earlier and unauthenticated users can access admin-level Gutenverse functionality.

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

Update Gutenverse to the latest version (1.8.6 or later) which should contain the authorization fix, and audit user roles/permissions after patching.

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-2023-35875 — 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-2023-35875 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