dbcve.org
ArmemberWordPress extension · Reputeinfosystems

CVE-2024-27995

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-21
Fix available
A fix is available. Upgrade to 4.0.24 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 Repute Infosystems ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup allows Stored XSS.This issue affects ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup: from n/a through 4.0.23.

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 ARMember WordPress membership plugin versions through 4.0.23 allows authenticated attackers to inject malicious JavaScript code via unsanitized user input fields (such as member registration/profile fields). The payload executes when other users or administrators view the affected content.

MitigationUpdate ARMember plugin to version 4.0.24 or later which contains the patched input sanitization. If immediate update is not possible, implement output encoding on user-generated content and consider temporarily restricting user registration capabilities.

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
ArmemberWordPress extension
Affected:< 4.0.24

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. Check installed ARMember plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > locate ARMember and view the Version column, or check the plugin header in wp-content/plugins/armember/plugin.php
    Affected if version is 4.0.23 or earlier (versions below 4.0.24 are affected)
  2. Verify user registration is enabled
    Go to WordPress Settings > General > ensure "Membership" is checked (Anyone can register), or check ARMember settings > General Settings > Registration status
    Affected if user registration is enabled and the plugin version is vulnerable (authentication required for attack)
  3. Review custom registration/profile fields
    Go to ARMember > Forms > select your registration or profile forms and inspect each field for any existing XSS payloads in field labels, descriptions, or default values
    Affected if any field contains malicious script content (indicates active exploitation)
  4. Inspect user profile data for XSS payloads
    Navigate to ARMember > Members > View Members and examine custom field values stored in member profiles; check for script tags, javascript:, or HTML event handlers in fields like custom text inputs
    Affected if any user profile contains unsanitized script content in custom fields

You are affected if ARMember plugin version is 4.0.23 or earlier AND user registration with custom fields is enabled, as this provides the attack surface for stored XSS injection.

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 4.0.24 or later
Fixed in 4.0.24
Interim mitigation

Update ARMember plugin to version 4.0.24 or later which contains the patched input sanitization. If immediate update is not possible, implement output encoding on user-generated content and consider temporarily restricting user registration capabilities.

Recommended fix High confidence

ARMember version 4.0.24

  1. 1. Back up your WordPress site database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.0.24
  5. 5. Alternatively, go to Dashboard > Updates and select ARMember to update
  6. 6. After updating, verify the plugin version shows 4.0.24 or higher
  7. 7. Test membership functionality, content restriction, and user registration to ensure the update did not break existing features
Caveat Minor plugin updates may include functionality changes; test in staging environment if concerned

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

Fix this in Armember Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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