CVE-2023-47842
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Zachary Segal CataBlog.This issue affects CataBlog: from n/a through 1.7.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCataBlog plugin through version 1.7.0 contains an unrestricted file upload vulnerability allowing attackers to upload files with dangerous types (e.g., executable PHP files) without proper validation. This could enable remote code execution on the underlying web server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify CataBlog plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'CataBlog' in the list of installed plugins.Affected if CataBlog appears in the installed plugins list
-
Check installed CataBlog versionIn the WordPress admin under Plugins > Installed Plugins, find CataBlog and note the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file (usually /wp-content/plugins/catablog/lib/catablog.php or similar) for the 'Version' header in the plugin comments.Affected if Version is 1.7.0 or any earlier version (1.0.x through 1.7.0)
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that CataBlog shows as 'Active' rather than 'Inactive'. The vulnerability requires the plugin to be active and its upload functionality to be accessible.Affected if Plugin status is Active
-
Verify upload functionality exposureCheck if the CataBlog upload endpoint is accessible by attempting to access the upload form or checking the plugin's upload handling code. This typically involves checking if /wp-admin/admin-ajax.php or a dedicated upload endpoint responds to upload-related actions from the plugin.Affected if Upload functionality is reachable and accepts file uploads without strict validation
If CataBlog plugin version 1.7.0 or earlier is installed and active, the environment contains the unrestricted file upload vulnerability described in this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based file type validation for uploads, store uploaded files outside the web root or with no-script/execute permissions, and verify file contents (magic bytes) rather than relying solely on file extensions or MIME types.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47842 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47842 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data