dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68558

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 averta Depicter Slider depicter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Depicter Slider: from n/a through <= 4.0.4.

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 Depicter Slider plugin for WordPress has a missing authorization vulnerability allowing users to exploit incorrectly configured access control security levels. This enables authenticated attackers (with subscriber-level or higher access) to perform actions that should require higher privileges. The vulnerability exists in versions up to and including 4.0.4.

MitigationApply the vendor patch when released; in the interim, restrict user registration and ensure users are assigned only the minimum required role. Verify that all admin actions in the plugin require appropriate capability checks (e.g., manage_options).

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify Depicter Slider plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Depicter Slider' or check the plugins directory for the 'depicterslider' folder
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Depicter Slider, and note the version number displayed under the plugin name
    Affected if Version is 4.0.4 or lower (any version up to and including 4.0.4)
  3. Check if user registration is enabled
    Go to WordPress Settings > General and look for the 'Membership' setting; verify whether 'Anyone can register' is checked
    Affected if Anyone can register is enabled, creating potential attackers with subscriber-level access
  4. Identify users with subscriber-level or higher roles
    Go to WordPress Users > All Users and review the role column; note any users assigned Subscriber, Contributor, Author, Editor, or Administrator roles
    Affected if There are users with roles other than Administrator who have access to the site, as these roles can exploit the missing authorization check

The environment is affected if the Depicter Slider plugin is installed at version 4.0.4 or lower AND the site has non-administrator users (especially subscriber-level accounts) who could exploit the missing authorization.

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

Apply the vendor patch when released; in the interim, restrict user registration and ensure users are assigned only the minimum required role. Verify that all admin actions in the plugin require appropriate capability checks (e.g., manage_options).

Recommended fix Moderate confidence

Depicter Slider version > 4.0.4 (consult WordPress plugin repository or vendor for exact latest secure version)

  1. 1. Check the current installed version of Depicter Slider plugin in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. If a newer version of Depicter Slider is available (version > 4.0.4), update the plugin to the latest version
  4. 4. Verify the update completed successfully
  5. 5. Test that the plugin functionality works as expected after the update
  6. 6. If no update is available from the WordPress repository, contact the plugin vendor (averta) directly for the patched version
Caveat Review the plugin's changelog for any breaking changes between your current version and the new version before updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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