dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-10681

MEDIUM · 6.3 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 The ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 4.0.51. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute arbitrary shortcodes.

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 ARMember WordPress plugin up to version 4.0.51 allows authenticated users with subscriber-level privileges to execute arbitrary shortcodes due to improper validation of a user-supplied value before passing it to the do_shortcode() function. This enables attackers to potentially invoke any registered WordPress shortcode with the permissions of their user account.

MitigationUpdate the ARMember plugin to version 4.0.52 or later which contains proper validation for the shortcode parameter. Until updated, consider restricting subscriber-level user capabilities or monitoring for suspicious shortcode-related requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 if ARMember plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the file /wp-content/plugins/armember/ folder, or query the wp_options table for 'active_plugins'
    Affected if ARMember plugin is present in the WordPress installation
  2. Determine installed ARMember version
    Check the plugin header in /wp-content/plugins/armember/armember.php for 'Version:' value, or view the installed version in Plugins > Installed Plugins list
    Affected if Version is 4.0.51 or lower (any version up to and including 4.0.51)
  3. Verify subscriber-level user accounts exist
    Navigate to WordPress admin > Users, or query the wp_users and wp_usermeta tables to identify users with the 'subscriber' role
    Affected if Any user account with subscriber-level privileges exists in the system
  4. Confirm shortcode functionality is accessible to subscribers
    Review ARMember plugin settings for any shortcode-related features (e.g., arm_single template shortcode) and verify that subscriber role has permission to access pages containing these shortcodes
    Affected if Subscriber users can access pages or features that render ARMember shortcodes without additional capability checks

If ARMember version 4.0.51 or lower is installed AND subscriber-level user accounts exist with access to shortcode-rendering functionality, the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ARMember plugin to version 4.0.52 or later which contains proper validation for the shortcode parameter. Until updated, consider restricting subscriber-level user capabilities or monitoring for suspicious shortcode-related requests.

Recommended fix Moderate confidence

Version 4.0.52 or later (latest stable release)

  1. Update the ARMember plugin to the latest available version from the WordPress plugin repository
  2. Navigate to Dashboard > Plugins > All Plugins in WordPress admin
  3. Locate ARMember in the plugin list
  4. Click 'Update Now' if an update is available, or reinstall the latest version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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