dbcve.org
BridgeWordPress extension · Edwiser

CVE-2024-49311

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 3.0.8 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WisdmLabs Edwiser Bridge edwiser-bridge allows Stored XSS.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

Stored Cross-site Scripting (XSS) vulnerability in Edwiser Bridge plugin allows authenticated attackers to inject malicious JavaScript into web pages via unsanitized user input that gets stored and rendered to other users.

MitigationUpdate Edwiser Bridge to the latest patched version. If no update is available, implement output encoding and input validation on all user-supplied data before storage and display.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Edwiser Bridge plugin is installed
    Access your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Edwiser Bridge' in the list of active plugins.
    Affected if Edwiser Bridge appears in the installed plugins list
  2. Determine installed version number
    In the Plugins list, find Edwiser Bridge and note the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and open the main plugin file (usually edwiser-bridge.php or similar) to read the Version header in the plugin comments.
    Affected if Version number is visible and is below 3.0.8
  3. Compare version against affected range
    Take the installed version number and compare it numerically to 3.0.8. Any version starting with 3.0.x below 3.0.8, or any version below 3.0.0, is within the affected range.
    Affected if Installed version is less than 3.0.8
  4. Confirm authentication vector
    Determine if user registration or profile fields are accessible to authenticated users. Edwiser Bridge handles Moodle-WordPress integration, so check if user profile fields, registration forms, or course enrollment data can be submitted by users with accounts on the system.
    Affected if User input fields are present and accessible to authenticated users

You are affected if Edwiser Bridge is installed and the installed version is below 3.0.8, as this is a stored XSS requiring authenticated user input capability.

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 output encoding and input validation on all user-supplied data before storage and display.

Recommended fix High confidence

Edwiser Bridge 3.0.8 or later

  1. Create a full backup of your WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Edwiser Bridge' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 3.0.8 or later from the WordPress repository or WisdmLabs
  5. After updating, verify the plugin version shows 3.0.8 or higher
  6. Clear any site caching mechanisms if applicable
  7. Test the functionality to ensure the plugin works correctly after the update

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

Fix this in Bridge 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-49311 — 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-49311 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