LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47672: WordPress WP Category Post List Widget Plugin <= 2.0.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Swashata WP Category Post List Widget.This issue affects WP Category Post List Widget: from n/a through 2.0.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47672 is a CSRF issue in the WordPress WP Category Post List Widget plugin up to 2.0.3. An attacker would need to trick an authenticated user into taking an action, potentially causing an unintended plugin-related change. The documented impact is limited to integrity, not data theft or service outage.

Executive priority

Prioritize this as a routine WordPress hygiene item unless the plugin is widely deployed on important sites. It requires user interaction and has limited documented impact, but exposed WordPress admin workflows should still be remediated or de-risked.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Swashata WP Category Post List Widget through version 2.0.3. CVSS 3.1 is 4.3: network attack vector, 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 with the WP Category Post List Widget plugin installed at version 2.0.3 or earlier. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. CSRF generally depends on a targeted authenticated user interacting with attacker-controlled content, so urgency is lower than unauthenticated remote code execution but still relevant for WordPress administration risk.

Researcher notes

The provided sources do not identify the exact vulnerable action, endpoint, proof of concept, fixed version, or operational workaround. Avoid assuming exploitability beyond the CVSS and CSRF classification. Validation should focus on asset presence, version status, and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and version.
  • Check the vendor, WordPress plugin page, and Patchstack for current remediation guidance.
  • Update if a fixed release is available from trusted sources.
  • If no fix is available, disable or remove the plugin where business impact allows.
  • Limit administrative access and reinforce caution with unsolicited links.

Validation and detection

  • Confirm whether WP Category Post List Widget is installed.
  • Record the installed plugin version and flag version 2.0.3 or earlier.
  • Review vendor and Patchstack entries for any fixed version or mitigation.
  • Check recent admin activity for unexpected plugin or widget configuration changes.
  • Document unaffected sites where the plugin is absent.
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-47672 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-47672Attack 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
SwashataWP Category Post List Widgetwp-category-posts-list, 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.