dbcve.org
Stockists Manager For WoocommerceWordPress extension · Berocket

CVE-2022-2518

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to after 1.0.2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The Stockists Manager for Woocommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.2.1. This is due to missing nonce validation on the stockist_settings_main() function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The Stockists Manager for WooCommerce plugin versions up to 1.0.2.1 lack nonce validation on the stockist_settings_main() function, allowing unauthenticated attackers to forge requests that modify plugin settings. Successful exploitation enables injection of malicious scripts (stored XSS) that execute when administrators view the affected settings pages.

MitigationAdd proper nonce verification to the stockist_settings_main() function and all admin action handlers; update to the latest patched version when available; audit other admin functions for similar CSRF vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Stockists Manager For WoocommerceWordPress extension
Affected:<= 1.0.2.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
    Check if the Berocket Stockists Manager For Woocommerce plugin is installed in your WordPress environment. Navigate to WP-Admin > Plugins and look for 'Berocket Stockists Manager For Woocommerce' or check the directory wp-content/plugins/ for a folder containing 'stockists' or 'berocket' in the name.
    Affected if The plugin is present in the plugins directory
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and find Berocket Stockists Manager For Woocommerce. The version number is displayed below the plugin name. Alternatively, open the main plugin PHP file (usually named stockists-manager-for-woocommerce.php or similar in the plugin folder) and look for the 'Version' header in the plugin comment block.
    Affected if The version is 1.0.2.1 or lower (any version up to and including 1.0.2.1)
  3. Examine the vulnerable function for nonce validation
    Access the plugin source code in wp-content/plugins/[plugin-folder]/. Locate the stockist_settings_main() function (or similar naming like stockist_settings). Open the PHP file containing this function and inspect the function code for the presence of nonce verification using wp_verify_nonce(), check_admin_referer(), or nonce_field().
    Affected if The stockist_settings_main() function exists and lacks nonce verification code (no wp_verify_nonce, check_admin_referer, or nonce_field calls)
  4. Confirm admin settings access is available
    Log into WordPress admin panel and navigate to the plugin settings page (typically under WooCommerce > Stockists or a dedicated Berocket settings menu). Verify the settings page loads and accepts input.
    Affected if Admin can access and modify plugin settings and the settings page is publicly accessible or accepts unauthenticated POST requests

You are affected if the Berocket Stockists Manager For Woocommerce plugin is installed with version 1.0.2.1 or lower AND the stockist_settings_main() function lacks nonce validation, allowing settings to be modified via forged requests leading to stored XSS.

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
Upgrade available Upgrade to a release after 1.0.2.1
Interim mitigation

Add proper nonce verification to the stockist_settings_main() function and all admin action handlers; update to the latest patched version when available; audit other admin functions for similar CSRF vulnerabilities.

Recommended fix Moderate confidence

Latest available version > 1.0.2.1 (check WordPress plugin repository for current stable release)

  1. Check if a newer version of the Stockists Manager for WooCommerce plugin is available in the WordPress plugin repository
  2. If a newer version exists, navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Locate Stockists Manager for WooCommerce and click Update Now if an update is available
  4. Alternatively, download the latest version from wordpress.org/plugins/stockists-manager-for-woocommerce and upload it via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin settings are configured correctly

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

Fix this in Stockists Manager For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA2.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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