WeformsWordPress extension · Weformspro
CVE-2023-51524
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 weForms.This issue affects weForms: from n/a through 1.6.18.
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 confidenceMissing Authorization vulnerability in weForms plugin allows authenticated users to perform actions they should not have permission to access. The specific endpoints or actions affected are not detailed in available sources, but authorization checks are missing or improperly implemented for certain form management operations.
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
WeformsWordPress extension
< 1.6.19CVSS 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.
-
Identify weForms plugin versionCheck the installed weForms version through WordPress admin (Plugins > weForms) or inspect the main plugin file header for the 'Version' fieldAffected if The installed version is below 1.6.19 (e.g., 1.6.18, 1.6.17, etc.)
-
Confirm weForms Pro editionVerify if the site is running weForms Pro (the Pro edition is explicitly listed as affected in the vulnerability details)Affected if The site uses weForms Pro version prior to 1.6.19
-
Review user roles with form management accessNavigate to WordPress admin > Users > Roles or check form-related capabilities assigned to user accounts, particularly focusing on roles below Administrator levelAffected if Non-administrator user accounts exist with form creation, editing, or deletion capabilities on a vulnerable weForms Pro version
A user is affected if weForms Pro version is below 1.6.19 and there are non-administrator users with form management capabilities in the WordPress environment
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.6.19
Update weForms to version 1.6.19 or later which contains the authorization fix. If immediate update is not possible, restrict user permissions and audit existing user accounts with form management capabilities.
weForms version 1.6.19
- Upgrade weForms plugin to version 1.6.19 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Weforms
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51524 — 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-51524 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