dbcve.org
BerqwpWordPress extension · Berqier

CVE-2024-37942

HIGH · 7.2 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.7.6 or later.
See remediation →
81/100
Remediation priority · High
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
Server-Side Request Forgery (SSRF) vulnerability in Berqier Ltd BerqWP.This issue affects BerqWP: from n/a through 1.7.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

Server-Side Request Forgery (SSRF) vulnerability in BerqWP plugin allows attackers to make the web server perform arbitrary HTTP requests to internal or external resources. This can enable access to internal services, cloud metadata endpoints (e.g., AWS169.254.169.254), or internal network infrastructure.

MitigationUpdate BerqWP to the latest version when available. If no patch exists, implement URL allowlist validation to restrict requests to trusted domains and block access to internal IP ranges and cloud metadata endpoints.

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
BerqwpWordPress extension
Affected:< 1.7.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm BerqWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BerqWP - Automated WordPress SEO Plugin' or check the wp-content/plugins/ directory for a berqwp folder.
    Affected if BerqWP plugin is present on the WordPress site
  2. Identify installed BerqWP version
    In WordPress admin, go to Plugins > Installed Plugins > BerqWP and view the version number displayed, or read the 'berqwp.php' file header in wp-content/plugins/berqwp/ for the 'Version' field.
    Affected if Version is lower than 1.7.6 or version cannot be determined (indicating an old or unmaintained installation)
  3. Locate BerqWP API endpoints
    Check the plugin files in wp-content/plugins/berqwp/ for PHP files handling HTTP requests. Look for functions using wp_remote_get, wp_remote_post, or similar WordPress HTTP API functions that accept user-controlled URLs. Common paths include includes/, classes/, or api/ subdirectories.
    Affected if Plugin contains code that makes outbound HTTP requests based on user input or external parameters
  4. Identify URL-fetching functionality
    Search plugin files for parameters accepting URLs or domains (search for 'url', 'endpoint', 'uri', 'domain' in GET/POST requests). Check for AJAX handlers or admin-ajax.php hooks that may accept URL parameters.
    Affected if Any feature accepts URL input without strict allowlist validation or IP range blocking

A site is affected if BerqWP is installed and the version is below 1.7.6, and the plugin exposes functionality that allows arbitrary URL submissions for HTTP requests.

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 1.7.6 or later
Fixed in 1.7.6
Interim mitigation

Update BerqWP to the latest version when available. If no patch exists, implement URL allowlist validation to restrict requests to trusted domains and block access to internal IP ranges and cloud metadata endpoints.

Recommended fix Moderate confidence

BerqWP version 1.7.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find BerqWP in the plugin list
  4. If an update is available, click 'Update Now' to update to version 1.7.6 or later
  5. Alternatively, use WP-CLI command: wp plugin update berqwp
  6. Verify the update was successful by checking the plugin version

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

Fix this in Berqwp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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