dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4610

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 Stored Cross-Site Scripting via the 'pm_author_message' parameter in the pm_send_message_to_author function in all versions up to, and including, 5.9.9.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability was partially patched in version 5.9.8.5.

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 has a Stored XSS vulnerability in the pm_send_message_to_author function. The pm_author_message parameter lacks proper input sanitization and output escaping, allowing authenticated attackers with Subscriber-level access to inject arbitrary JavaScript that executes when users view affected pages.

MitigationUpdate the ProfileGrid plugin to the latest version beyond 5.9.9.2. If updates are unavailable, implement input sanitization using WordPress sanitization functions (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) on the pm_author_message parameter.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm ProfileGrid plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate ProfileGrid, or check /wp-content/plugins/ directory for the profilegrid-user-profiles-groups-and-communities folder
    Affected if ProfileGrid plugin is not installed on the WordPress site
  2. Identify installed ProfileGrid version
    In WordPress admin, click on ProfileGrid in the plugins list to view the version number, or inspect the main plugin file (e.g., profilegrid-user-profiles-groups-and-communities.php) for the Version header
    Affected if The installed version is at or below 5.9.9.2 (versions up to and including 5.9.9.2 are affected)
  3. Verify pm_send_message_to_author feature is accessible
    Check if the author messaging feature is enabled in ProfileGrid settings (ProfileGrid > Settings > General or Messaging settings), and confirm the pm_author_message parameter is processed by the plugin
    Affected if The messaging functionality is enabled and the plugin processes pm_author_message POST/GET parameters
  4. Inspect plugin source code for missing sanitization
    Locate the pm_send_message_to_author function in the plugin files (typically in includes/ or public/ folders) and check if pm_author_message is processed without sanitize_text_field or similar WordPress sanitization functions
    Affected if The pm_author_message parameter is handled without input sanitization (no sanitize_text_field, sanitize_html_class, etc.) and without output escaping (no esc_html, esc_attr, etc.) when displayed
  5. Look for injected scripts in message content
    Check the WordPress database (typically wp_pm_new_messages or similar tables) for any message records containing script tags, javascript:, or event handlers (onerror, onload, onclick) in the message content fields
    Affected if Malicious script tags or JavaScript event handlers are found stored in the message content

A site is affected if ProfileGrid plugin version 5.9.9.2 or lower is installed, the messaging feature is enabled, and the pm_author_message parameter is processed without proper sanitization and escaping.

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 the ProfileGrid plugin to the latest version beyond 5.9.9.2. If updates are unavailable, implement input sanitization using WordPress sanitization functions (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) on the pm_author_message parameter.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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