Woostagram ConnectWordPress extension · Asepbagjapriandana
CVE-2024-49327
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 bepitulaz Woostagram Connect woostagram-connect allows Upload a Web Shell to a Web Server.This issue affects Woostagram Connect: from n/a through <= 1.0.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 · moderate confidenceThe Woostagram Connect plugin for WordPress contains an unrestricted file upload vulnerability allowing attackers to upload executable scripts (web shells) directly to the web server's document root. The plugin fails to validate file types or sanitize uploaded files, enabling remote code execution upon access to the uploaded malicious script.
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
Woostagram ConnectWordPress extension
<= 1.0.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 if Woostagram Connect plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'woostagram-connect' or containing 'woostagram' and list its contents.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify the installed plugin versionOpen the main plugin file (typically woostagram-connect.php or similar in the plugin folder) and locate the version declaration in the plugin header comment, or check the readme.txt file for the 'Stable tag' version.Affected if The version number returned is 1.0.2 or lower.
-
Locate the plugin's file upload functionalitySearch the plugin files for upload-related code: look for functions containing 'upload', 'wp_upload_bits', 'move_uploaded_file', or 'wp_handle_upload'. Identify the form action or AJAX endpoint handling uploads.Affected if The plugin contains file upload handling code and the upload functionality is present and accessible.
-
Verify upload directory is web-accessibleCheck the plugin configuration or code to determine the upload path. By default, WordPress uploads go to wp-content/uploads/. Verify this directory is accessible via HTTP from the web.Affected if Uploaded files can be accessed directly via a web browser, allowing execution of uploaded scripts.
A WordPress site is affected if it has Woostagram Connect plugin version 1.0.2 or lower installed with the file upload feature accessible and the upload directory web-accessible, allowing remote code execution.
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, store uploaded files outside the web root, disable script execution in upload directories, and apply any available vendor patches.
Fix this in Woostagram Connect
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49327 — 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-2024-49327 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