Social Auto PosterWordPress extension · Wpwebinfotech
CVE-2024-6756
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 · uneditedThe Social Auto Poster plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'wpw_auto_poster_get_image_path' function in all versions up to, and including, 5.3.14. This makes it possible for authenticated attackers, with Contributor-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible. An attacker can use CVE-2024-6754 to exploit with subscriber-level access.
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 Social Auto Poster WordPress plugin lacks file type validation in the wpw_auto_poster_get_image_path function, allowing authenticated users with Contributor-level or higher permissions to upload arbitrary files. This can lead to remote code execution. The vulnerability affects all versions up to 5.3.14 and can be chained with CVE-2024-6754 for subscriber-level exploitation.
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
Social Auto PosterWordPress extension
< 5.3.15CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Social Auto Poster plugin is installedCheck the WordPress plugins directory or use wp-cli: wp plugin list --status=active --format=csv | grep -i 'social-auto-poster'Affected if The plugin is active and installed
-
Determine the installed plugin versionCheck the plugin header in wp-content/plugins/social-auto-poster/social-auto-poster.php for the Version field, or use: wp plugin get social-auto-poster --format=jsonAffected if Version is less than 5.3.15 (e.g., 5.3.14, 5.3.13, etc.)
-
Identify users with Contributor-level or higher rolesQuery WordPress users with wp user list --role=contributor --format=count, or check Users > All Users in wp-admin for any users assigned Contributor, Author, Editor, or Administrator rolesAffected if Any users exist with Contributor, Author, Editor, or Administrator roles who could trigger the vulnerable function
-
Inspect upload directory for unexpected file typesExamine wp-content/uploads/ and plugin upload folders for newly created files with extensions like .php, .phtml, .exe, or other executable types that were not intentionally uploadedAffected if Unexpected executable files appear in upload directories, especially in plugin-related paths
-
Check for suspicious admin or plugin-specific usersReview WordPress users for accounts that may have been created automatically by the plugin or added by an attackerAffected if Unknown administrator accounts exist or plugin-created user accounts appear unexpectedly
If the Social Auto Poster plugin version is below 5.3.15 and users with Contributor-level or higher permissions exist in the WordPress installation, the environment is vulnerable to arbitrary file upload and potential 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.
dbcve · scoped5.3.15
Update the Social Auto Poster plugin to the latest version immediately. If immediate updating is not possible, disable the plugin or implement web application firewall rules to block executable file uploads.
Social Auto Poster version 5.3.15
- 1. Backup your WordPress site and database before making any changes.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find 'Social Auto Poster' in the plugin list.
- 5. If an update is available, click 'Update Now' to update to version 5.3.15.
- 6. Alternatively, download version 5.3.15 from the official WordPress plugin repository or CodeCanyon.
- 7. Deactivate the existing plugin, delete it, then upload and install the updated version.
- 8. After update, verify the plugin is running version 5.3.15 under Plugins > Installed Plugins.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Social Auto Poster
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6756 — 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-6756 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