LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47516: WordPress Category Post List Widget Plugin <= 2.0 is vulnerable to Cross Site Scripting (XSS)

Cross-Site Request Forgery (CSRF) vulnerability in Stark Digital Category Post List Widget allows Stored XSS.This issue affects Category Post List Widget: from n/a through 2.0.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-47516 affects the WordPress Category Post List Widget plugin through version 2.0. A CSRF weakness can lead to stored cross-site scripting, meaning an attacker may trick a user into causing malicious content to persist on the site. Sources rate it high severity, but do not show known active exploitation.

Executive priority

Treat as high priority for WordPress environments that use this plugin. The issue can affect site integrity and visitor trust, but urgency should be scoped to confirmed plugin deployments because the bundle does not show active exploitation.

Technical view

The CVE describes a CSRF issue in Stark Digital Category Post List Widget that enables stored XSS. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges required, user interaction required, and changed scope. The source bundle identifies affected versions through 2.0 and CWE-352.

Likely exposure

Exposure is limited to WordPress installations running Stark Digital Category Post List Widget through version 2.0. The bundle does not identify affected CPEs or a fixed version, so plugin inventory is the key first step.

Exploitation context

The bundle does not cite CISA KEV listing or active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF-to-stored-XSS risk, but the sources do not provide exploit maturity details.

Researcher notes

Evidence is concise and does not include patch status, proof-of-concept details, or exploitation telemetry. Avoid assuming broader product impact. Focus validation on plugin presence, version, and stored-content review while tracking vendor or Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the category-post-list-widget plugin.
  • Check vendor and Patchstack guidance for a fixed or recommended version.
  • Update the plugin if a trusted fixed release is available.
  • Disable or remove the plugin where no safe version is confirmed.
  • Review affected sites for unauthorized stored content changes.

Validation and detection

  • Confirm whether Category Post List Widget is installed and its version.
  • Verify whether any installation is version 2.0 or older.
  • Check Patchstack and vendor sources for current remediation guidance.
  • Review pages using the widget for unexpected script-like content.
  • Confirm no untrusted administrators or editors changed widget settings.
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-47516 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-47516Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
Stark DigitalCategory Post List Widgetcategory-post-list-widget, 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.