dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2022-46845

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
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 Essential Plugin Slider a SlidersPack allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Slider a SlidersPack: from n/a before 2.3.

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 Slider a SlidersPack WordPress plugin before version 2.3 contains a missing authorization vulnerability where incorrectly configured access control security levels allow unauthenticated or unauthorized users to access functionality that should be restricted. This authorization bypass occurs due to improper checks on sensitive operations within the plugin.

MitigationUpdate the Slider a SlidersPack plugin to version 2.3 or later which contains proper authorization controls. Before updating, ensure a full backup of the site is created and test the update in a staging environment.

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. Verify Slider a SlidersPack plugin is installed
    Log in to WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Slider a SlidersPack' in the list of active plugins.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin name 'Slider a SlidersPack' to view its details. Note the version number displayed.
    Affected if The installed version is earlier than 2.3 (for example, 2.2, 2.1, 1.x, or any version number below 2.3).
  3. Identify publicly accessible slider endpoints
    Review your website for any published sliders or shortcodes that render slider content on the frontend. Check if these pages are accessible without authentication.
    Affected if Slider content is publicly accessible without requiring logged-in status or admin privileges.
  4. Inspect plugin access control settings
    Navigate to the plugin settings page in WordPress admin (typically under SlidersPack or a dedicated settings menu). Look for any security level, access control, or permission settings that control who can create, edit, or view sliders.
    Affected if The plugin settings show宽松 (permissive) access controls or no authorization checks are enforced for sensitive operations.

A user is affected if the Slider a SlidersPack plugin version is below 2.3 AND the plugin is active on their WordPress site with accessible slider 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Slider a SlidersPack plugin to version 2.3 or later which contains proper authorization controls. Before updating, ensure a full backup of the site is created and test the update in a staging environment.

Recommended fix Moderate confidence

Version 2.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Slider a SlidersPack' (also known as Essential Addons for Elementor - Slider Pack or similar) plugin
  4. Check the current installed version
  5. If the installed version is before 2.3, click 'Update Now' to update to the latest version
  6. Alternatively, navigate to Dashboard > Updates and apply any available updates
  7. After updating, verify the plugin version is 2.3 or later
  8. Test the slider functionality to ensure the update did not break existing features

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

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-2022-46845 — 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-2022-46845 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