dbcve.org
Custom Field TemplateWordPress extension · Wpgogo

CVE-2023-38392

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-07
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.9 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 reflected cross-site scripting (XSS) vulnerability in Hiroaki Miyashita Custom Field Template WordPress plugin versions 2.5.9 and earlier allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the plugin's HTTP responses.

MitigationUpdate the Custom Field Template plugin to version 2.6.0 or later which contains the patched code with proper input sanitization and output encoding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Field TemplateWordPress extension
Affected:< 2.6.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Custom Field Template plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'custom-field-template' or 'custom-field-template-cft'
    Affected if The plugin folder exists in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, find the Custom Field Template plugin in the plugins list and read the version number under the plugin name, or open the main plugin PHP file (usually custom-field-template.php) and look for the 'Version:' header comment
    Affected if The displayed version is 2.5.9 or earlier, or less than 2.6.0
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Custom Field Template plugin shows as 'Active'
    Affected if The plugin is active and the version is vulnerable (2.5.9 or earlier)
  4. Identify the product name in use
    Check the plugin folder name and main file headers - the affected product may appear as 'Custom Field Template', 'Custom Field Template (by Wpgogo)', or 'Wpgogo Custom Field Template'
    Affected if The product name matches Custom Field Template or Wpgogo Custom Field Template and the version is in the vulnerable range

Your environment is affected if the Custom Field Template (or Wpgogo Custom Field Template) plugin is installed, active, and running version 2.5.9 or earlier (any version below 2.6.0).

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.

dbcve · scoped
Upgrade available Upgrade to 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Update the Custom Field Template plugin to version 2.6.0 or later which contains the patched code with proper input sanitization and output encoding.

Recommended fix High confidence

Custom Field Template version 2.6.0 or latest stable release

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the Custom Field Template plugin by Hiroaki Miyashita
  5. 5. If an update to version 2.6.0 or higher is available, click 'Update Now'
  6. 6. Alternatively, download version 2.6.0 or latest from the WordPress Plugin Repository
  7. 7. Deactivate the current plugin version, then upload and install the updated version
  8. 8. Reactivate the plugin after upgrade
Caveat Review plugin settings after upgrade as default configurations may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Custom Field Template Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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