LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22695: WordPress Custom Field Template Plugin <= 2.5.8 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.8 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-22695 is a CSRF issue in the WordPress Custom Field Template plugin through version 2.5.8. A logged-in user could be tricked into causing an unintended plugin-related action. Published impact is limited integrity loss, not data theft or outage. The source bundle does not identify a fixed version or active exploitation.

Executive priority

Treat as a routine but time-bound WordPress hygiene issue. Prioritize internet-facing sites, administrator-heavy workflows, and sites where plugin configuration changes could affect business content integrity.

Technical view

The record maps to CWE-352 with CVSS 3.1 score 4.3: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. Exploitation requires user interaction but no attacker authentication. Scope is unchanged, with low integrity impact and no confidentiality or availability impact. Sources identify Hiroaki Miyashita Custom Field Template as affected through 2.5.8.

Likely exposure

Exposure is limited to WordPress sites using the Custom Field Template plugin at version 2.5.8 or earlier. Sites not running this plugin are not indicated as affected by the provided sources.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The attack model is CSRF: an attacker would need to induce a user with a relevant active WordPress session to interact with attacker-controlled content.

Researcher notes

Evidence is narrow: CVE metadata and Patchstack identify CSRF in the plugin through 2.5.8, with CVSS indicating user interaction and low integrity impact. The bundle does not provide affected endpoints, nonce details, fixed version, proof of exploitation, or compensating controls.

Mitigation direction

  • Inventory WordPress sites for the Custom Field Template plugin and version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version.
  • Update the plugin if a supported fixed release is available.
  • Disable or remove the plugin where it is unnecessary or unsupported.
  • Reinforce administrator phishing awareness for CSRF-style interaction risks.

Validation and detection

  • Confirm whether each WordPress site has Custom Field Template installed.
  • Record installed plugin versions and flag 2.5.8 or earlier.
  • Review plugin change logs or vendor notices for a CSRF fix.
  • Check logs for suspicious administrator-side plugin setting changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-22695 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-22695Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Hiroaki MiyashitaCustom Field Templatecustom-field-template, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.