SqueezeWordPress extension · Squeeze Project
CVE-2024-35767
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 Bogdan Bendziukov Squeeze allows Code Injection.This issue affects Squeeze: from n/a through 1.4.
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 confidenceAn unrestricted file upload vulnerability in Bogdan Bendziukov Squeeze versions up to 1.4 allows attackers to upload files with dangerous types (e.g., executable scripts like PHP) that can be subsequently accessed and executed, leading to code injection and potential 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
SqueezeWordPress extension
< 1.4.1CVSS 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.
-
Identify Squeeze installation versionLocate the Squeeze application files and check the version number in the source code, configuration, or version file. Common locations include a version.php, composer.json, or a changelog file in the project root.Affected if The installed version is Squeeze Project Squeeze and the version is less than 1.4.1 (or the version cannot be determined and the application is from an unverified source).
-
Locate the file upload functionalitySearch the application source code for file upload handlers, forms accepting file input, or upload endpoints. Look for $_FILES usage, multipart form handling, or upload-related functions in the codebase.Affected if The application contains file upload code that accepts user-submitted files without proper validation checks.
-
Determine where uploaded files are storedExamine the upload handling code to identify the destination directory for uploaded files. Check if the path is within the web document root (htdocs, public_html, www) or outside of it.Affected if Uploaded files are stored in a directory accessible via HTTP/HTTPS (within the web root).
-
Check if script execution is permitted in upload directoriesReview the web server configuration (Apache .htaccess, nginx config) and the upload directory for any restrictions on executing uploaded files. Look for directives like 'php_flag engine off' or similar execution restrictions.Affected if The upload directory allows execution of script files (PHP, ASP, JSP, etc.) and there are no security restrictions blocking execution.
A user is affected if they are running Squeeze Project Squeeze version below 1.4.1, the application has an accessible file upload feature, and uploaded files can be stored in a web-accessible location where they can be executed.
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.4.1
Implement strict allowlist-based file type validation, verify file content/magic bytes rather than just extension, store uploads outside the web root, and disable script execution in upload directories.
Squeeze 1.4.1
- Backup your WordPress site before making any changes
- Update the Squeeze plugin to version 1.4.1 or later through the WordPress admin dashboard (Plugins > Updates)
- Alternatively, upload Squeeze version 1.4.1 or later via Plugins > Add New > Upload Plugin
- Verify the update was successfully applied by checking the plugin version in Plugins > Installed Plugins
- Confirm the vulnerability is resolved by testing file upload functionality if applicable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Squeeze
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35767 — 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-35767 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