LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45605: WordPress Feed Statistics Plugin <= 4.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Christopher Finke Feed Statistics plugin <= 4.1 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45605 affects the WordPress Feed Statistics plugin from Christopher Finke. The reported issue is CSRF, meaning an authenticated site administrator could be tricked into causing an unintended plugin action. The business impact is limited in the source bundle: integrity impact is low, with no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate maintenance risk, not an emergency. Address it during normal WordPress plugin patching, with faster action for public or business-critical sites where administrators frequently manage content.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Feed Statistics plugin versions up to 4.1. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required by the attacker, but user interaction is required. The bundle does not identify a fixed version, patch details, or exploit technique.

Likely exposure

Exposure is likely limited to WordPress sites with the Feed Statistics plugin installed, especially versions 4.1 or earlier. The affected package is listed as wordpress-feed-statistics, but the bundle provides no CPEs and incomplete version metadata.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation would require user interaction, consistent with a CSRF issue, and the documented impact is limited to low integrity impact.

Researcher notes

Evidence is sparse. The bundle confirms CSRF, CWE-352, CVSS 4.3, and an affected range in the title and description, but it does not provide CPEs, fixed-version data, affected functions, or public exploit evidence.

Mitigation direction

  • Inventory WordPress sites for the Feed Statistics plugin and installed versions.
  • If running version 4.1 or earlier, review vendor or Patchstack guidance for a fix.
  • If no maintained fix is available, disable or remove the plugin after business approval.
  • Prioritize remediation on administrator-facing or high-value WordPress sites.

Validation and detection

  • Confirm whether wordpress-feed-statistics is installed on each WordPress instance.
  • Compare installed plugin versions against the <=4.1 affected range.
  • Review admin activity logs for unexpected Feed Statistics changes.
  • Document vendor guidance or fixed-version evidence before closing the finding.
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-45605 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-45605Attack 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
Christopher FinkeFeed Statisticswordpress-feed-statistics, 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.