SymbiostockWordPress extension
CVE-2023-49814
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 Symbiostock symbiostock.This issue affects Symbiostock: from n/a through 6.0.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 confidenceUnrestricted file upload vulnerability in Symbiostock plugin versions up to 6.0.0 allows attackers to upload dangerous file types (e.g., executable scripts, PHP files) without proper validation, potentially enabling remote code execution on the server.
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
SymbiostockWordPress extension
<= 6.0.0CVSS 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.
-
Verify Symbiostock plugin versionLog into WordPress admin, navigate to Plugins > Installed Plugins, locate Symbiostock and check the version number displayed. Alternatively, inspect the main plugin file (e.g., /wp-content/plugins/symbiostock/symbiostock.php) and look for the 'Version' header in the plugin comments.Affected if The installed version is 6.0.0 or lower.
-
Confirm file upload functionality is activeCheck if the Symbiostock upload feature is accessible by navigating to the Symbiostock settings or upload page in the WordPress admin dashboard. Verify that the upload form is functional and not disabled.Affected if The upload functionality is present and enabled on the site.
-
Inspect upload directory configurationCheck the wp-content/uploads/symbiostock directory (or similar) for .htaccess configuration. Look for directives that allow or restrict script execution (e.g., 'RemoveHandler', 'AddType', or lack thereof). Also verify directory permissions allow write access.Affected if The upload directory lacks executable restrictions (no .htaccess blocking PHP/executable files, or server config allows script execution in upload paths).
-
Check WordPress media upload settingsNavigate to Settings > Media in WordPress admin and verify if unfiltered uploads are enabled, or check if the site allows uploads of dangerous file types in wp-config.php (ALLOW_UNFILTERED_UPLOADS constant).Affected if Unfiltered uploads are enabled or no server-side file type validation is enforced.
If Symbiostock version 6.0.0 or lower is installed with the upload feature enabled and the upload directory permits executable files, the environment is vulnerable to CVE-2023-49814.
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 server-side file type validation (allowlist approach) for file extensions and MIME types, with additional validation via file content magic bytes; restrict upload directories to non-executable locations.
Fix this in Symbiostock
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49814 — 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-49814 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