LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47842: WordPress CataBlog plugin <= 1.7.0 - Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in Zachary Segal CataBlog.This issue affects CataBlog: from n/a through 1.7.0.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-47842 is a critical file-upload flaw in the WordPress CataBlog plugin through version 1.7.0. A high-privileged authenticated user could upload dangerous file types, potentially leading to full compromise of site data, content integrity, and availability.

Executive priority

Treat as urgent for any WordPress estate using CataBlog. Prioritize inventory first, then remove, disable, or patch according to trusted vendor guidance, especially on public-facing business sites.

Technical view

The issue is CWE-434, unrestricted upload of files with dangerous types, affecting Zachary Segal CataBlog up to 1.7.0. CVSS 3.1 is 9.1 with network access, low complexity, high privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations running the CataBlog plugin through 1.7.0. The CVSS vector indicates an attacker needs high privileges, so compromised administrator-level accounts or malicious trusted users are the main concern.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Risk remains serious because arbitrary dangerous file uploads can become site takeover when performed by a sufficiently privileged WordPress user.

Researcher notes

Evidence is sparse beyond the CVE record and Patchstack entry. Do not assume unauthenticated exploitation; CVSS states high privileges are required. Confirm plugin presence, exact version, and whether any maintained fixed release exists before declaring closure.

Mitigation direction

  • Inventory WordPress sites for the CataBlog plugin and version.
  • Check vendor, WordPress plugin, and Patchstack guidance for a supported fix.
  • Remove or disable CataBlog where it is unnecessary or unsupported.
  • Restrict high-privilege WordPress access to trusted, MFA-protected accounts.
  • Review upload controls and file execution restrictions on affected sites.

Validation and detection

  • Confirm whether CataBlog is installed and at or below version 1.7.0.
  • Review administrator and high-privilege WordPress accounts for compromise indicators.
  • Check webserver upload directories for unexpected executable file types.
  • Review application and webserver logs for suspicious upload activity.
  • Document whether a vendor-supported remediation path exists.
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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47842 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2023-47842Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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
Zachary SegalCataBlogcatablog, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.