Form MakerWordPress extension · 10web
CVE-2023-48290
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 · uneditedImproper Restriction of Excessive Authentication Attempts vulnerability in 10Web Form Builder Team Form Maker by 10Web allows Functionality Bypass.This issue affects Form Maker by 10Web: from n/a through 1.15.20.
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 confidenceThe Form Maker plugin before version 1.15.21 contains an improper restriction of excessive authentication attempts vulnerability. The plugin fails to properly limit the number of failed authentication attempts, allowing attackers to bypass authentication mechanisms through brute force or excessive login attempts.
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 MakerWordPress extension
< 1.15.21CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Form Maker plugin is installedCheck your WordPress installation's plugin directory or use the WordPress admin dashboard to confirm the 10web Form Maker plugin is present and active.Affected if The Form Maker plugin by 10web is installed and active in WordPress.
-
Check installed plugin versionLocate the main Form Maker plugin file (typically in wp-content/plugins/ form-maker directory) and read the plugin header or version file to obtain the exact version number installed.Affected if The installed version number is lower than 1.15.21.
-
Confirm authentication features are in useCheck if the Form Maker plugin has any login forms, authentication-related forms, or user submission forms configured that handle credentials or session attempts.Affected if The plugin contains or is configured to handle authentication, login, or user credential submission forms.
Your environment is affected if the 10web Form Maker plugin is installed with a version lower than 1.15.21 and contains authentication or login form functionality.
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.15.21
Update Form Maker by 10Web to version 1.15.21 or later. If patching is not immediately possible, implement supplementary rate limiting at the web application firewall (WAF) or web server level to restrict authentication attempts.
1.15.21
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find 'Form Maker by 10Web' in the plugin list
- Click 'Update now' if an update is available, or manually download version 1.15.21 from the WordPress plugin repository and upload it
- Verify the plugin updated successfully by checking the version number
- Optionally, test the password/login functionality to confirm the authentication attempt limit is now enforced
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Form Maker
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-2023-48290 — 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-48290 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