Upload Fields For WpformsWordPress extension · Softlabbd
CVE-2024-35661
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 · uneditedMissing Authorization vulnerability in SoftLab Upload Fields for WPForms.This issue affects Upload Fields for WPForms: 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 confidenceA Missing Authorization vulnerability in SoftLab Upload Fields for WPForms plugin versions through 1.0.2 allows unauthenticated or low-privilege attackers to access sensitive functionality, likely file upload operations, without proper permission checks. The CVSS 9.8 indicates critical impact, possibly enabling arbitrary file uploads or manipulation of form submissions.
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
Upload Fields For WpformsWordPress 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 plugin is installedNavigate to WP Admin > Plugins and look for 'Softlabbd Upload Fields For Wpforms' or 'Upload Fields for WPForms' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check installed versionIn WP Admin > Plugins, click 'View Details' on the SoftLab Upload Fields plugin to display the version numberAffected if The version listed is 1.0.2 or lower
-
Identify active upload form configurationsCheck WPForms > Forms for any forms using upload field types; inspect the form builder for fields added via the SoftLab pluginAffected if Any WPForms contain upload fields created by this plugin
-
Review file upload directoriesInspect the wp-content/uploads directory for any recently created files with unusual extensions or from unknown sourcesAffected if Unexpected file types or unexpected files appear in upload directories
-
Check for unauthorized form submissionsReview WPForms > Entries for any submissions from unexpected users or IP addresses, especially forms with file uploadsAffected if Form entries exist from users who should not have access or are unauthenticated
The environment is affected if the SoftLab Upload Fields for WPForms plugin is installed at version 1.0.2 or lower and contains active upload form configurations accessible to unauthorized users.
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 dataUpdate to the latest version of Upload Fields for WPForms which includes proper authorization checks. If no patch is available, disable the plugin until a fixed version is released.
Fix this in Upload Fields For Wpforms
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-35661 — 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-35661 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