dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-13741

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 5.9.4.3 or later.
See remediation →
60/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 ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to Limited Server-Side Request Forgery in all versions up to, and including, 5.9.4.2 via the pm_upload_image function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to download and view images, as well as validating if a non-image file exists, both on local or remote hosts.

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 ProfileGrid WordPress plugin contains a limited Server-Side Request Forgery (SSRF) vulnerability in the pm_upload_image function, affecting all versions up to 5.9.4.2. Authenticated attackers with Subscriber-level access can make web requests from the server to arbitrary locations, allowing them to probe internal services, download images, and validate file existence on local or remote hosts.

MitigationUpdate the ProfileGrid plugin to version 5.9.5 or later, which should contain a patch for this SSRF vulnerability. As a temporary workaround, restrict subscriber-level access to sensitive features until the patch can be applied.

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
ProfilegridWordPress extension
Affected:< 5.9.4.3

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 ProfileGrid plugin installation
    Navigate to WordPress admin > Plugins and locate ProfileGrid in the installed plugins list, or check the plugin files in /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/ for version information
    Affected if ProfileGrid plugin is not found or not installed
  2. Check installed ProfileGrid version
    In WordPress admin, go to Plugins > Installed Plugins > ProfileGrid and note the version number displayed, or read the main plugin PHP file header for 'Version:' field
    Affected if Version is less than 5.9.4.3 (including all versions up to 5.9.4.2)
  3. Confirm subscriber-level user existence
    In WordPress admin, go to Users and verify if any users exist with the Subscriber role, or check user_roles in wp_usermeta for 'subscriber' role assignment
    Affected if Subscriber-level users exist in the WordPress installation
  4. Verify plugin feature access for subscribers
    Check ProfileGrid plugin settings under Groups or Global Settings to confirm if subscriber role has permission to use upload features, or test by logging in as a subscriber and attempting to access pm_upload_image function
    Affected if Subscriber role has permission to access the upload image functionality

You are affected if ProfileGrid plugin is installed with a version below 5.9.4.3 AND subscriber-level users exist with access to the upload image feature.

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

Update the ProfileGrid plugin to version 5.9.5 or later, which should contain a patch for this SSRF vulnerability. As a temporary workaround, restrict subscriber-level access to sensitive features until the patch can be applied.

Recommended fix High confidence

5.9.4.3

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the ProfileGrid plugin in the list
  4. 4. Click 'Update Now' if an update is available, or manually upload version 5.9.4.3 or higher from the WordPress plugin repository
  5. 5. Verify the installed version shows 5.9.4.3 or later in the plugins list
  6. 6. Test that user profile image upload functionality works correctly

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

Fix this in Profilegrid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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