BridgeWordPress extension · Edwiser

CVE-2024-49312

HIGH · 8.6 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 3.0.8 or later.
See remediation →
95/100
Remediation priority · Urgent
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 WisdmLabs Edwiser Bridge edwiser-bridge.This issue affects Edwiser Bridge: from n/a through <= 3.0.7.

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 Edwiser Bridge plugin allows an attacker to induce the server to make requests to arbitrary destinations by manipulating input parameters used in server-side request functions. This can lead to internal service enumeration, cloud metadata exposure, or pivot attacks.

MitigationUpdate Edwiser Bridge to the latest patched version. If no update is available, implement strict allow-listing of permitted URL destinations and validate all user-supplied URLs before use in server-side requests.

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
BridgeWordPress extension
Affected:< 3.0.8

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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. Locate Edwiser Bridge plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'Edwiser Bridge' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'edwiser-bridge'.
    Affected if The plugin is installed and active
  2. Identify installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on 'Edwiser Bridge' to view the version number displayed in the plugin details. Alternatively, check the main plugin file header in wp-content/plugins/edwiser-bridge/ for the 'Version' field.
    Affected if The version is less than 3.0.8 (for example, 3.0.7, 3.0.6, etc.)
  3. Confirm plugin is actively processing remote requests
    Check the plugin settings at Settings > Edwiser Bridge or within the Edwiser Bridge menu options. Look for any configuration that involves importing courses, connecting to external Moodle instances, or fetching remote data that accepts a user-supplied URL.
    Affected if Remote request features are enabled and configurable with custom URLs
  4. Verify plugin file integrity
    If possible, compare the plugin files against a known clean installation of the same version, focusing on files that handle HTTP requests (typically in includes/ or class files within the plugin folder).
    Affected if Modified or unexpected files exist in the plugin directory

A user is affected if Edwiser Bridge is installed with a version lower than 3.0.8 AND the plugin or its settings allow user-supplied URLs to be used in server-side 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 3.0.8 or later
Fixed in 3.0.8
Interim mitigation

Update Edwiser Bridge to the latest patched version. If no update is available, implement strict allow-listing of permitted URL destinations and validate all user-supplied URLs before use in server-side requests.

Recommended fix Moderate confidence

3.0.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Edwiser Bridge (edwiser-bridge) plugin
  4. Check if the current version is below 3.0.8
  5. If vulnerable, click 'Update Now' if an update to version 3.0.8 is available, or manually download version 3.0.8 from a trusted source and reinstall
  6. After updating, verify the new version number reflects 3.0.8 or higher
  7. Test critical functionality (course imports, connections to external LMS) to ensure the update did not break existing features

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

Fix this in Bridge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-49312 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