dbcve.org
MemberpressWordPress extension · Caseproof

CVE-2024-5025

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-22
Fix available
A fix is available. Upgrade to 1.11.30 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
The Memberpress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘arglist’ parameter in all versions up to, and including, 1.11.29 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Memberpress WordPress plugin fails to properly sanitize and escape the 'arglist' parameter, allowing authenticated users with Contributor-level permissions or higher to inject malicious JavaScript that executes when other users view affected pages. This stored XSS affects all versions up to 1.11.29.

MitigationUpgrade Memberpress to version 1.11.30 or later which contains proper input sanitization and output escaping for the 'arglist' parameter.

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
MemberpressWordPress extension
Affected:< 1.11.30

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 Memberpress plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Memberpress and check the Version number, or check the plugin header in /wp-content/plugins/memberpress/memberpress.php
    Affected if Version is 1.11.29 or lower (any version below 1.11.30)
  2. Confirm authenticated user access
    Review WordPress user roles on the site. Check if any users have Contributor-level or higher permissions by navigating to Users in the WordPress admin panel
    Affected if Any user with Contributor, Author, Editor, or Administrator role exists on the site
  3. Identify affected parameter usage
    Search WordPress database or plugin files for usage of the 'arglist' parameter in forms, shortcodes, or URLs. Check memberpress.php and related files for code handling this parameter
    Affected if The 'arglist' parameter is present in custom Memberpress configurations, custom forms, or URL parameters
  4. Review stored content for malicious payloads
    Search WordPress database posts and postmeta tables for any stored scripts or unusual HTML attributes in Memberpress-related content, particularly in any fields that might accept the arglist parameter
    Affected if Malicious JavaScript code is found stored in WordPress content related to Memberpress

The environment is affected if Memberpress version is below 1.11.30 AND authenticated users with Contributor-level or higher access exist AND the 'arglist' parameter feature is in use

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.11.30 or later
Fixed in 1.11.30
Interim mitigation

Upgrade Memberpress to version 1.11.30 or later which contains proper input sanitization and output escaping for the 'arglist' parameter.

Recommended fix High confidence

Memberpress 1.11.30

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Dashboard > Plugins in WordPress admin
  3. 3. Locate the Memberpress plugin in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.11.30
  5. 5. Alternatively, download Memberpress version 1.11.30 from the official WordPress repository or memberpress.com and upload/install it manually
  6. 6. After updating, verify the plugin version shows 1.11.30 or higher
  7. 7. Clear any caching layers if your site uses caching plugins or CDN

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

Fix this in Memberpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.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-2024-5025 — 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-5025 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