dbcve.org
MemberpressWordPress extension · Caseproof

CVE-2024-1412

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 1.11.27 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
The Memberpress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘message’ and 'error' parameters in all versions up to, and including, 1.11.26 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Note - the issue was partially patched in 1.11.25, but could still potentially be exploited under some circumstances.

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 is vulnerable to reflected Cross-Site Scripting (XSS) via the 'message' and 'error' parameters in versions up to 1.11.26. Insufficient input sanitization and inadequate output escaping allow unauthenticated attackers to inject arbitrary JavaScript through malicious links that trick users into clicking them. The vulnerability was partially patched in version 1.11.25 but remains exploitable under certain conditions.

MitigationUpdate MemberPress to the latest version available from the vendor, as complete patches for the input sanitization and output escaping issues have been released.

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.27

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. Check MemberPress plugin version installed
    Log into WordPress admin, go to Plugins > Installed Plugins > MemberPress, and read the version number displayed. Alternatively, check the main plugin file (memberpress/main.php) for the 'Version' header in the plugin comments.
    Affected if Version is lower than 1.11.27 (e.g., 1.11.26, 1.11.25, or earlier)
  2. Verify the plugin is actively loaded
    Confirm MemberPress is installed and activated in WordPress. The vulnerability is only exploitable when the plugin code is running.
    Affected if Plugin is installed and active with a version below 1.11.27
  3. Identify endpoints using message or error parameters
    Search MemberPress code for $_GET or $_REQUEST handling of 'message' and 'error' parameters. Check files like memberpress.php, class-memberpress.php, or any controller handling front-end requests.
    Affected if The site processes requests containing 'message' or 'error' query parameters without proper escaping

You are affected if MemberPress plugin version is below 1.11.27 and your site processes the 'message' or 'error' parameters in URLs that get reflected back to users without sanitization.

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.27 or later
Fixed in 1.11.27
Interim mitigation

Update MemberPress to the latest version available from the vendor, as complete patches for the input sanitization and output escaping issues have been released.

Recommended fix High confidence

1.11.27

  1. Backup your WordPress site database and files before proceeding with any updates
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate Memberpress in the plugin list
  5. Click the 'Update now' link or button next to Memberpress if an update is available, or manually upload version 1.11.27
  6. Verify the updated version number reflects 1.11.27 after the update completes
  7. Test critical Memberpress functionality (membership access, payment processing, subscription management) to confirm the update did not break existing functionality
Caveat Minor plugin version upgrades typically do not introduce breaking changes; however, always test in a staging environment before deploying to production

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

Fix this in Memberpress 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-1412 — 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-1412 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