LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47238: WordPress Top 10 Plugin <= 3.3.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WebberZone Top 10 – WordPress Popular posts by WebberZone plugin <= 3.3.2 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects the WebberZone Top 10 WordPress popular-posts plugin through version 3.3.2. A malicious site could trick a logged-in site user into triggering unintended plugin actions. The public sources rate it high, but they do not describe the exact vulnerable action or name a fixed version.

Executive priority

Prioritize this as high for WordPress sites using the affected plugin, especially public or revenue-facing sites. Treat missing fix information as a reason to verify vendor guidance quickly, not as proof of safety.

Technical view

CVE-2023-47238 is a CWE-352 CSRF flaw in package top-10, WebberZone Top 10. The CVSS 3.1 vector is 8.8 high: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, and high confidentiality, integrity, and availability impact. Source detail is limited.

Likely exposure

Exposure is likely limited to WordPress installations running WebberZone Top 10 plugin version 3.3.2 or earlier. Sites without this plugin, or with versions not covered by the source, are not evidenced as affected.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. CSRF generally depends on inducing a logged-in user to interact with attacker-controlled content, but the public source does not provide the specific vulnerable workflow.

Researcher notes

Public detail is sparse: the bundle identifies CSRF, affected plugin, version ceiling, CWE, and CVSS, but not the vulnerable endpoint, required victim role, nonce behavior, fixed version, or exploit observations. Avoid asserting more without vendor detail.

Mitigation direction

  • Inventory WordPress sites for the WebberZone Top 10 plugin.
  • Check WebberZone, WordPress.org, or Patchstack guidance for a fixed release.
  • Upgrade if a vendor-confirmed fixed version is available.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict administrative access and reinforce anti-phishing controls for WordPress users.

Validation and detection

  • Confirm whether package top-10 is installed on each WordPress site.
  • Record installed versions and flag any instance at 3.3.2 or earlier.
  • Check vendor or Patchstack advisories for fixed-version confirmation.
  • Review recent plugin-setting and admin activity for unexpected changes.
  • Verify backups and restoration paths for affected WordPress sites.
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-47238 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
WebberZoneTop 10 – WordPress Popular posts by WebberZonetop-10, 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.