LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45753: WordPress which template file Plugin <= 4.6.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Gilles Dumas which template file plugin <= 4.6.0 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45753 is a cross-site request forgery issue in the WordPress “which template file” plugin from Gilles Dumas, reported for versions up to 4.6.0. A successful attack would require user interaction and is rated medium, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate-priority WordPress plugin hygiene issue. It is not shown as actively exploited, but affected sites should be inventoried and remediated because CSRF can cause unauthorized changes when a logged-in user is tricked into interacting with malicious content.

Technical view

The source bundle identifies CWE-352 CSRF in the which-template-file WordPress plugin <= 4.6.0. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, score 4.3. Sources do not describe the vulnerable action, endpoint, exploit details, or a specific fixed version.

Likely exposure

Exposure is limited to WordPress sites with the Gilles Dumas “which template file” plugin installed at affected versions up to 4.6.0. The bundle does not identify affected CPEs, other products, hosting providers, or downstream packages beyond package name which-template-file.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires user interaction, consistent with CSRF risk, but the public details provided do not specify the exact action an attacker could trigger.

Researcher notes

Public evidence is sparse. The CVE and Patchstack entry establish CSRF, affected plugin, and medium severity, but do not provide endpoint-level details, proof-of-concept status, or a named patched version in the supplied bundle. Avoid assuming broader impact without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for the which-template-file plugin and installed version.
  • Check Patchstack and vendor or WordPress plugin guidance for a fixed release.
  • Update the plugin if a supported fixed version is available.
  • Disable or remove the plugin where it is unnecessary or no fix is available.
  • Prioritize admin-session hygiene for users managing affected WordPress sites.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the exact installed plugin version and compare it with <= 4.6.0 exposure.
  • Check vendor, WordPress.org, or Patchstack notes for remediation status.
  • Review recent administrative changes for unexpected plugin-related activity.
  • Document any compensating controls if the plugin cannot be removed or updated.
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-45753 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-45753Attack 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
Gilles Dumaswhich template filewhich-template-file, 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.