dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-57665

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 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 Insecure Direct Object References (IDOR) in GravityView <= 3.0.0 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 IDOR vulnerability in GravityView plugin versions 3.0.0 and below allows unauthenticated attackers to access or modify objects (such as entries, views, or other data) by directly referencing object identifiers without proper authorization validation.

MitigationUpdate GravityView to a version newer than 3.0.0. If immediate update is not possible, restrict access to affected endpoints via web server configuration or disable the plugin until patched.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 GravityView plugin is installed
    Locate the GravityView plugin directory in the WordPress wp-content/plugins folder, typically named 'gravityview' or check via WordPress admin plugin list
    Affected if GravityView plugin files exist in the installation
  2. Determine installed GravityView version
    Open the main plugin file (gravityview.php) and locate the 'Version' header in the plugin comment block, or check the version constant defined in the plugin code
    Affected if The reported version is 3.0.0 or lower
  3. Verify plugin is active on the site
    Access WordPress admin under Plugins > Installed Plugins and confirm GravityView shows as 'Active', or query the wp_options table for the active_plugins option
    Affected if GravityView is activated on the WordPress site
  4. Confirm site is accessible to unauthenticated users
    Test that the WordPress site responds to requests without requiring login, as the IDOR flaw can be exploited by any unauthenticated visitor
    Affected if The site allows unauthenticated access to GravityView-generated pages or endpoints

If GravityView version 3.0.0 or below is installed and active on an accessible WordPress site, the environment is affected by this unauthenticated IDOR vulnerability.

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 GravityView to a version newer than 3.0.0. If immediate update is not possible, restrict access to affected endpoints via web server configuration or disable the plugin until patched.

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-57665 — 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-57665 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