dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-47691

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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
Improper Control of Generation of Code ('Code Injection') vulnerability in Ultimate Member Ultimate Member ultimate-member allows Code Injection.This issue affects Ultimate Member: from n/a through <= 2.10.3.

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

Code injection vulnerability in the Ultimate Member WordPress plugin (versions <= 2.10.3) allows attackers to inject malicious code due to improper control of code generation. The medium severity (CVSS 5.5) suggests the exploit may require some user interaction or authentication but can lead to arbitrary code execution on the affected WordPress site.

MitigationUpdate Ultimate Member plugin to the latest available version to patch the code injection vulnerability. If immediate update is not possible, restrict plugin access to trusted administrators and monitor for suspicious activity.

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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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. Verify Ultimate Member plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Ultimate Member'. Alternatively, check the file /wp-content/plugins/ultimate-member/ for existence, or run: wp plugin list --name='ultimate-member'
    Affected if The Ultimate Member plugin is present and active on the WordPress site
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on Ultimate Member to view version details. Or check the plugin main file header: /wp-content/plugins/ultimate-member/readme.txt or ultimate-member.php for 'Version:' field
    Affected if Installed version is 2.10.3 or lower (any version <= 2.10.3)
  3. Identify code generation features in plugin settings
    Navigate to Ultimate Member settings in WordPress admin. Look for sections related to Templates, Custom Code, Profile Builder, or any feature allowing users to create or modify PHP code, custom templates, or shortcodes
    Affected if Any feature permitting user-generated code or template injection is enabled and accessible to non-admin users
  4. Check for unauthorized user roles or permissions
    Go to Ultimate Member > Users > Roles or general WordPress User Roles. Review if any custom roles with elevated permissions exist, or if untrusted user accounts have been added with access to plugin configuration
    Affected if Non-administrator users have access to plugin settings or code generation features
  5. Inspect for signs of injected malicious code
    Check plugin template files in /wp-content/uploads/um_templates/ or custom template directories for unfamiliar PHP code, base64_decode calls, shell_exec, or eval functions. Also review wp-content/uploads/ for recently modified PHP files
    Affected if Suspicious PHP code found in template files or uploads directory indicating potential exploitation

A user is affected if Ultimate Member plugin version is 2.10.3 or lower AND any code generation or template feature is accessible to non-admin users, or if malicious code is already present in template files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ultimate Member plugin to the latest available version to patch the code injection vulnerability. If immediate update is not possible, restrict plugin access to trusted administrators and monitor for suspicious activity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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