dbcve.org
Wpcom MemberWordPress extension · Wpcom

CVE-2024-47378

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-05
Fix available
A fix is available. Upgrade to 1.5.4.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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Lomu WPCOM Member wpcom-member allows Reflected XSS.This issue affects WPCOM Member: from n/a through <= 1.5.4.

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

A reflected Cross-site Scripting (XSS) vulnerability exists in the WPCOM Member WordPress plugin (versions up to 1.5.4). The vulnerability stems from improper input neutralization during web page generation, allowing attackers to inject malicious scripts through unsanitized user inputs that get reflected back in HTTP responses.

MitigationUpdate WPCOM Member to the latest version after vendor release. If no patch is available, implement output encoding (esc_html, esc_attr, or similar functions) on all user-supplied inputs before rendering in HTML context.

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
Wpcom MemberWordPress extension
Affected:< 1.5.4.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 WPCOM Member plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPCOM Member' or check the wp-content/plugins directory for a folder named 'wpcom-member'
    Affected if The WPCOM Member plugin is found in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WPCOM Member, and view the version number displayed beneath the plugin name
    Affected if The installed version is lower than 1.5.4.1 (for example, 1.5.4, 1.5.3, etc.)
  3. Identify plugin-related URL parameters
    Review pages where the WPCOM Member plugin is active (such as login, registration, or member profile pages) and interact with forms or links to identify any query parameters in the URL
    Affected if The plugin exposes pages with URL parameters that could accept user input and reflect it back in the response
  4. Test for reflected input in HTTP responses
    Using a browser or HTTP tool, submit a benign test string (such as a unique alphanumeric value) as a parameter value on WPCOM Member pages and inspect the page source or response to see if the exact string appears without encoding
    Affected if User-supplied input is reflected back in the HTML response without proper encoding or sanitization

The environment is affected if the WPCOM Member plugin is installed with a version lower than 1.5.4.1 and the plugin exposes user input fields that reflect unsanitized values back in HTTP responses.

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.5.4.1 or later
Fixed in 1.5.4.1
Interim mitigation

Update WPCOM Member to the latest version after vendor release. If no patch is available, implement output encoding (esc_html, esc_attr, or similar functions) on all user-supplied inputs before rendering in HTML context.

Recommended fix High confidence

1.5.4.1 or latest available version

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the WPCOM Member plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.5.4.1 or later.
  5. 5. Alternatively, you can manually download version 1.5.4.1 or latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 1.5.4.1 or higher under Plugins > Installed Plugins.

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

Fix this in Wpcom Member Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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