EleformsWordPress extension · Theinnovs
CVE-2024-6626
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 · uneditedThe EleForms – All In One Form Integration including DB for Elementor plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on several functions in all versions up to, and including, 2.9.9.9. This makes it possible for unauthenticated attackers to view form submissions.
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 confidenceThe EleForms plugin for WordPress has a Broken Access Control vulnerability where several functions lack proper capability checks, allowing unauthenticated attackers to access form submission data via Insecure Direct Object Reference (IDOR). This affects all versions up to 2.9.9.9.
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
EleformsWordPress extension
<= 2.9.9.9CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 EleForms plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'EleForms' or 'Theinnovs Eleforms'. Note whether it is active or inactive.Affected if The plugin is installed and active, making the vulnerable code accessible.
-
Check installed plugin versionIn the plugins list, find the EleForms entry and note the version number displayed. Compare this to the affected range of <= 2.9.9.9.Affected if The installed version is 2.9.9.9 or lower (any version up to and including 2.9.9.9 is affected). Versions 2.9.9.1 and later contain the fix, so 2.9.9.0 or below is vulnerable.
-
Identify form submission endpointsReview the site for any publicly accessible URLs that handle form submissions or retrieve form data. Common patterns include endpoints with 'eleform', 'form-submission', 'form-data', or 'submission' in the URL path.Affected if The site exposes form submission endpoints that do not require authentication.
-
Test unauthenticated access to submission dataUsing a tool like curl or a browser, attempt to access form submission or data retrieval endpoints without providing any authentication credentials. Observe whether the server returns form submission data.Affected if The server returns form submission data or sensitive information without requiring login or capability verification.
-
Check for IDOR vulnerability in form data retrievalSubmit a request to a form data endpoint attempting to access submission records by modifying identifier parameters (such as form IDs, submission IDs, or record numbers). Verify if different numeric IDs return different users submission data.Affected if Different ID values in the request return different users form submissions, indicating Insecure Direct Object Reference.
You are affected if the EleForms plugin is active, installed at version 2.9.9.9 or lower, and form submission endpoints are accessible without authentication or allow access to other users submissions via IDOR.
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 · scopedUpdate to version 2.9.9.1 or later which includes proper capability checks. Until updated, restrict access to form submission endpoints at the server level.
Upgrade to a version newer than 2.9.9.9 (check WordPress plugin repository for latest stable release)
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the EleForms plugin
- 4. If an update is available, click 'Update Now'
- 5. Verify the update completes successfully
- 6. Confirm the running version is newer than 2.9.9.9
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Eleforms
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6626 — 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-6626 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