Wp Githuber MdWordPress extension · Terryl
CVE-2023-47846
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 Terry Lin WP Githuber MD.This issue affects WP Githuber MD: from n/a through 1.16.2.
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 · high confidenceThe WP Githuber MD WordPress plugin versions up to 1.16.2 contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (such as executable scripts) without proper validation, potentially leading to remote code execution on the affected WordPress site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Githuber MdWordPress extension
< 1.16.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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.
-
Locate the WP Githuber MD plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-githuber-md', 'githuber-md', or similar variant of the pluginAffected if The plugin folder exists in the plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file and look for the version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entryAffected if The version listed is below 1.16.3 (e.g., 1.16.2, 1.16.1, etc.)
-
Determine if the markdown file upload feature is activeAccess the plugin settings through WordPress admin (Settings > Githuber MD) and check if the file upload or markdown import functionality is enabledAffected if The file upload/import feature is turned on in the plugin settings
-
Inspect the upload directory configurationCheck the wp-content/uploads directory for any recently uploaded files with extensions such as .php, .phtml, .php5, or other executable types that may indicate exploitationAffected if Suspicious executable files are found in upload directories that correspond to the plugin's upload functionality
A user is affected if the WP Githuber MD plugin is installed with a version lower than 1.16.3 and the file upload feature is enabled in the plugin settings.
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.
dbcve · scoped1.16.3
Implement strict server-side file type validation, whitelist allowed extensions only, and update to the latest patched version of the plugin when available.
WP Githuber MD version 1.16.3
- Backup your WordPress site before making any changes
- Update the WP Githuber MD plugin to version 1.16.3 or later through the WordPress admin dashboard (Plugins > WP Githuber MD > Update Now)
- Verify the plugin version is now 1.16.3 or higher under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Githuber Md
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47846 — 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-47846 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