LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45654: WordPress Comments Ratings Plugin <= 1.1.7 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Pixelgrade Comments Ratings plugin <= 1.1.7 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45654 is a CSRF flaw in the WordPress Comments Ratings plugin from Pixelgrade affecting versions up to 1.1.7. A successful attack could cause an unintended action with limited integrity impact if a user is tricked into interacting with malicious content. The provided sources do not show active exploitation.

Executive priority

Treat this as a scheduled WordPress hygiene item, not an emergency, unless the plugin is broadly deployed on high-value public sites. Prioritize confirmation of plugin use and vendor-supported remediation.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in package comments-ratings, Pixelgrade Comments Ratings for WordPress, <=1.1.7. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the Comments Ratings plugin installed at version 1.1.7 or earlier. The bundle does not identify affected endpoints, required victim role, or whether vulnerable installations are common.

Exploitation context

The CVE is not listed in KEV, and the supplied sources do not cite active exploitation. CSRF generally requires convincing a user to interact with attacker-controlled content while their browser can perform an unintended authenticated action.

Researcher notes

Evidence is sparse. The bundle provides CVSS, CWE, product, package name, affected version boundary, and a Patchstack reference, but not vulnerable endpoint details, proof of exploitation, or a named fixed release.

Mitigation direction

  • Inventory WordPress sites for the comments-ratings plugin and recorded version.
  • Check Pixelgrade, WordPress plugin, and Patchstack guidance for a fixed version.
  • Upgrade if a vendor-confirmed fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • For maintained forks, enforce WordPress nonces and capability checks on state-changing requests.

Validation and detection

  • Confirm whether Comments Ratings is installed on each WordPress site.
  • Record whether any installation is version 1.1.7 or earlier.
  • Review vendor or Patchstack advisories for fixed-version status.
  • Verify state-changing plugin actions require CSRF protection before accepting user requests.
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-45654 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-45654Attack 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
PixelgradeComments Ratingscomments-ratings, 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.