dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2022-41791

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to after 5.1.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Auth. (subscriber+) CSV Injection vulnerability in ProfileGrid plugin <= 5.1.6 on WordPress.

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

The ProfileGrid WordPress plugin versions 5.1.6 and below contain an authenticated CSV Injection vulnerability. Users with subscriber-level permissions or higher can export data (likely user profiles) to CSV format, and by injecting formula characters (e.g., =, +, -, @) into profile fields, they can cause spreadsheet applications to execute arbitrary commands when the CSV is opened.

MitigationUpdate ProfileGrid to version 5.1.7 or later, which should include proper sanitization of CSV export fields to prevent formula injection.

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

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
High
Integrity
High
Availability
High

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

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 version
    In WordPress admin, go to Plugins > Installed Plugins and find ProfileGrid. Compare the version number to 5.1.6 or earlier.
    Affected if The installed version is 5.1.6 or below.
  2. Check if CSV export functionality exists
    Look for user profile export features in the WordPress admin under ProfileGrid settings or frontend user profile pages. Search the codebase for 'export' and 'csv' functions related to user data.
    Affected if CSV export functionality is present and accessible to authenticated users.
  3. Identify user roles with export access
    Review ProfileGrid user group settings to determine which roles (including subscriber-level) have permission to export user profile data to CSV.
    Affected if Subscriber-level or higher user roles can export data to CSV.
  4. Inspect profile fields for user input
    Check ProfileGrid profile field configurations to see which fields accept free-text user input that could contain formula characters (=, +, -, @).
    Affected if Profile fields accept unvalidated user input that can be included in CSV exports.

A user is affected if ProfileGrid version 5.1.6 or below is installed AND the CSV export feature is accessible to authenticated users with subscriber-level permissions or higher.

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 a release after 5.1.6
Interim mitigation

Update ProfileGrid to version 5.1.7 or later, which should include proper sanitization of CSV export fields to prevent formula injection.

Recommended fix Moderate confidence

ProfileGrid 5.1.7 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find ProfileGrid in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or ProfileGrid's website.
  6. 6. After updating, verify the plugin version shows 5.1.7 or higher.
  7. 7. Test user registration and CSV export functionality to confirm the fix 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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