dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-57759

HIGH · 8.8 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 7 weeks old

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
Unauthenticated Cross Site Request Forgery (CSRF) in ProfileGrid <= 5.9.9.7 versions.

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

Unauthenticated Cross Site Request Forgery (CSRF) vulnerability in ProfileGrid WordPress plugin versions 5.9.9.7 and below. The vulnerability allows attackers to craft malicious requests that can be executed without proper CSRF token validation, potentially enabling unauthorized actions on behalf of users.

MitigationUpdate ProfileGrid to a version newer than 5.9.9.7. If immediate update is not possible, consider disabling the plugin or implementing additional request validation at the web application firewall level.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check if ProfileGrid plugin is installed
    Locate the ProfileGrid plugin directory in the WordPress installation: inspect the /wp-content/plugins/ directory for folders starting with 'profilegrid' or 'ProfileGrid'. Alternatively, query the WordPress database table wp_options for option_name = 'active_plugins' and check if it contains 'profilegrid'.
    Affected if ProfileGrid plugin is present in the plugins directory or active in WordPress
  2. Determine installed ProfileGrid version
    Open the main ProfileGrid plugin file (commonly profile-magic.php or profilegrid.php) in the plugin directory and locate the 'Version' field in the plugin header comment. Alternatively, use WP-CLI command: wp plugin list --name='profilegrid' --format=json
    Affected if The installed version is 5.9.9.7 or lower (any version at or below 5.9.9.7)
  3. Confirm plugin is active on the site
    Check WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' and look for 'profilegrid' in the serialized array. Or use WP-CLI: wp plugin is-active profilegrid
    Affected if The plugin shows as active or enabled in WordPress

The site is affected if ProfileGrid plugin is installed, active, and running version 5.9.9.7 or below, because the missing CSRF token validation affects all plugin functionality in those versions.

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 ProfileGrid to a version newer than 5.9.9.7. If immediate update is not possible, consider disabling the plugin or implementing additional request validation at the web application firewall level.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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