dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57687

HIGH · 8.5 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 →
91/100
Remediation priority · Urgent
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
Contributor SQL Injection in Custom Field Template <= 2.7.8 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

SQL injection vulnerability in the Custom Field Template WordPress plugin affecting versions 2.7.8 and below. Users with Contributor-level permissions can inject malicious SQL queries through unsanitized input in custom field template functionality.

MitigationUpdate the Custom Field Template plugin to a version newer than 2.7.8. If no patched version is available, implement input validation/sanitization at the application layer or restrict contributor-level user capabilities until a fix is released.

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

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

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 Custom Field Template plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Custom Field Template'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for 'Version:' comment, typically in wp-content/plugins/custom-field-template/custom-field-template.php
    Affected if The installed version is 2.7.8 or lower
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that 'Custom Field Template' is activated (the plugin will show 'Activate' link absent and 'Deactivate' link present)
    Affected if The plugin is installed and activated
  3. Check for custom field template configuration
    In WordPress admin, go to Posts > Custom Field Template or Settings > Custom Field Template (depending on plugin version). Look for any saved custom field template configurations with defined field templates
    Affected if At least one custom field template is configured and saved in the plugin settings
  4. Identify Contributor-level users
    In WordPress admin, go to Users > All Users. Review the 'Role' column for any users assigned the 'Contributor' role
    Affected if There are users with Contributor-level permissions in the WordPress installation

If the Custom Field Template plugin version is 2.7.8 or below, the plugin is active, has custom field templates configured, and Contributor-level users exist in the environment, the installation is affected by this SQL injection 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 the Custom Field Template plugin to a version newer than 2.7.8. If no patched version is available, implement input validation/sanitization at the application layer or restrict contributor-level user capabilities until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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