dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-57681

MEDIUM · 6.4 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 →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 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
Subscriber Server Side Request Forgery (SSRF) in GeoDirectory <= 2.8.161 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

A Server Side Request Forgery (SSRF) vulnerability exists in the Subscriber functionality of the GeoDirectory WordPress plugin. Users with Subscriber-level privileges can potentially induce the server to make requests to arbitrary URLs, allowing access to internal services or data that should not be exposed.

MitigationUpdate GeoDirectory to a version newer than 2.8.161. If no update is available, implement URL validation and allowlist controls in the subscriber-facing functionality that handles URL parameters.

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. Identify GeoDirectory installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find GeoDirectory. Note the version number displayed. Alternatively, check the plugin file header in wp-content/plugins/geodirectory/geodirectory.php for the 'Version' tag.
    Affected if The installed version is 2.8.161 or lower.
  2. Confirm subscriber role is active
    Go to WordPress Users > Users and filter by Subscriber role, or check Users > User Roles in a role management plugin if installed. Verify that at least one subscriber account exists.
    Affected if Any subscriber-level user account exists in the WordPress installation.
  3. Check for subscriber-accessible URL submission features
    Navigate to the frontend of the site logged in as a Subscriber user. Look for any forms, search fields, or API endpoints that accept URL input, particularly in GeoDirectory listing submission or search functionality.
    Affected if The Subscriber role can access features that accept or process URL parameters.
  4. Verify URL validation is not applied
    If subscriber-accessible URL input fields exist, attempt to submit a request to an internal IP (e.g., 127.0.0.1) or internal hostname. Check server logs or response to see if the server attempts to fetch the internal resource.
    Affected if The server can be induced to make requests to arbitrary URLs through subscriber-accessible functionality without proper validation.

A user is affected if GeoDirectory version 2.8.161 or lower is installed AND subscriber-level users exist with access to URL-handling functionality.

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 GeoDirectory to a version newer than 2.8.161. If no update is available, implement URL validation and allowlist controls in the subscriber-facing functionality that handles URL parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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