LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45109: WordPress WhitePage Plugin <= 1.1.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in ZAKSTAN WhitePage plugin <= 1.1.5 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects WordPress sites using the ZAKSTAN WhitePage plugin version 1.1.5 or earlier. It is a CSRF issue, meaning an attacker may be able to trick a logged-in site administrator into unintentionally making a change. The cited sources do not show confirmed active exploitation.

Executive priority

Treat as a moderate WordPress hygiene issue. Prioritize confirmation across public-facing WordPress properties, then remediate affected plugin deployments through vendor-backed guidance or removal where unnecessary.

Technical view

CVE-2023-45109 is a CWE-352 Cross-Site Request Forgery vulnerability in WhitePage <= 1.1.5. The CVSS 3.1 score is 5.4, with network attack vector, low complexity, no attacker privileges, and required user interaction. Reported impact is low integrity and low availability, with no confidentiality impact.

Likely exposure

Exposure is limited to WordPress installations with the WhitePage plugin installed at version 1.1.5 or earlier. Practical risk depends on whether privileged users are logged in and can be induced to visit attacker-controlled content.

Exploitation context

The bundle marks CISA KEV status as false and provides no cited evidence of exploitation in the wild. The vulnerability requires user interaction, consistent with CSRF, and is most relevant to authenticated administrative workflows.

Researcher notes

Evidence is concise and does not include request details, vulnerable actions, or fixed-version metadata in the provided bundle. Avoid assuming exploitability beyond CSRF with required user interaction and low integrity/availability impact.

Mitigation direction

  • Identify all WordPress sites using the WhitePage plugin.
  • Check vendor or Patchstack guidance for a fixed version before updating.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict WordPress administrative access to trusted users and networks where feasible.
  • Review administrator security awareness around unsolicited links.

Validation and detection

  • Confirm whether plugin slug white-page-publication is installed.
  • Record the installed WhitePage version on each WordPress site.
  • Flag any instance running version 1.1.5 or earlier.
  • Review recent admin activity for unexpected content or configuration changes.
  • Track vendor advisory status for explicit patch guidance.
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-45109 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
5.4 (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:L

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-45109Attack 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:L

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
ZAKSTANWhitePagewhite-page-publication, 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.