Form BuilderWordPress extension · Web Settler
CVE-2023-23795
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Muneeb Form Builder plugin <= 1.9.9.0 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Muneeb Form Builder WordPress plugin versions 1.9.9.0 and below allows attackers to trick authenticated administrators into performing unintended actions such as modifying form settings or submitting malicious data by forging legitimate requests.
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
Form BuilderWordPress extension
<= 1.9.9.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if Web Settler Form Builder plugin is installedNavigate to WordPress Admin > Plugins and look for 'Web Settler Form Builder' or 'Muneeb Form Builder' in the installed plugins listAffected if Plugin is present in the plugins directory regardless of activation status
-
Verify the installed plugin versionIn WordPress Admin > Plugins, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/form-builder/ folder for the Version: x.x.x.x entry in the main PHP fileAffected if Version listed is 1.9.9.0 or lower
-
Confirm the plugin is activeIn WordPress Admin > Plugins, check if the plugin shows as 'Active' under its statusAffected if Plugin is currently activated and accessible to administrators
-
Check admin access exposureNavigate to the plugin settings page (typically under Form Builder or Settings in the admin sidebar) to confirm the admin interface is reachableAffected if Plugin settings page loads and accepts admin input, making CSRF attacks possible
You are affected if the Web Settler Form Builder or Muneeb Form Builder plugin is installed with version 1.9.9.0 or lower and is currently active, as this allows the CSRF vulnerability to be exploited against authenticated administrators.
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 Muneeb Form Builder plugin to the latest version to obtain the patched code that implements proper CSRF token validation, or disable the plugin if no update is available.
Fix this in Form Builder
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23795 — 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-23795 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