dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2022-45813

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in BeRocket Advanced AJAX Product Filters allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Advanced AJAX Product Filters: from n/a through 1.6.3.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

Missing authorization vulnerability in the BeRocket Advanced AJAX Product Filters WordPress plugin allows attackers to access functionality that should be restricted to authenticated users with proper capabilities. The plugin fails to enforce access control checks on certain AJAX endpoints, enabling unauthenticated or lower-privilege users to perform actions intended for administrators.

MitigationUpdate to the latest version of BeRocket Advanced AJAX Product Filters. If no update is available, temporarily disable the plugin or implement custom access controls at the web server level to restrict access to affected AJAX endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'BeRocket Advanced AJAX Product Filters' in the list of active plugins.
    Affected if The plugin is installed and activated on the WordPress site.
  2. Identify installed version
    In the plugins list, find the version number displayed under the plugin name 'BeRocket Advanced AJAX Product Filters'. Alternatively, check the plugin's main PHP file header for the 'Version' comment.
    Affected if The installed version is older than the patched version (any version lacking proper authorization checks on AJAX endpoints).
  3. Confirm AJAX functionality is in use
    Check if the plugin's AJAX endpoints are active by reviewing page source for JavaScript files referencing 'berocket_ajax' or by inspecting network requests when filtering products on the frontend.
    Affected if The plugin's AJAX functionality is enabled and processing filter requests on the site.
  4. Inspect AJAX endpoint access controls
    Use a web proxy or curl to send requests directly to the plugin's AJAX endpoints (commonly at /wp-admin/admin-ajax.php with 'action' parameter related to berocket filters) without authentication or with a low-privilege user account.
    Affected if The AJAX endpoints respond to requests from unauthenticated users or users without administrator capabilities, returning expected filter data or performing actions that should require higher privileges.
  5. Review user role capabilities
    Create a test subscriber or contributor account and attempt to access what should be restricted admin AJAX actions provided by this plugin, if such endpoints exist.
    Affected if Lower-privilege users can execute AJAX actions that should be restricted to administrators.

A site is affected if BeRocket Advanced AJAX Product Filters is installed with AJAX functionality enabled and its AJAX endpoints accept requests without proper authorization verification for user capabilities.

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 to the latest version of BeRocket Advanced AJAX Product Filters. If no update is available, temporarily disable the plugin or implement custom access controls at the web server level to restrict access to affected AJAX endpoints.

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