CVE-2026-110383
validatedZero produced an exploit or a check.GHSA-pjjv-c28j-37gf ↗EUVD-2026-103426 ↗
description
WP E-Signature Electronic Signature Add-on for Fluent Forms versions through 2.0.5 are affected by an authorization bypass involving user-controlled access keys. An unauthenticated remote attacker may access protected resources when access-control settings are incorrectly configured.
mitigation
Restrict access to the affected add-on and review its access-control configuration to prevent user-controlled keys from granting unintended access. Upgrade to a vendor-provided fixed release when one is published.
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-18 11:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-110383
{ "etk_id": "ETK-2026-1967", "cve_id": "CVE-2026-110383", "display_id": "CVE-2026-110383", "ghsa_id": "GHSA-pjjv-c28j-37gf", "euvd_id": "EUVD-2026-103426", "status": "published", "anchor_state": "anchored", "title": "Authorization bypass in Fluent Forms E-Signature add-on", "summary": "WP E-Signature Electronic Signature Add-on for Fluent Forms versions through 2.0.5 are affected by an authorization bypass involving user-controlled access keys. An unauthenticated remote attacker may access protected resources when access-control settings are incorrectly configured.", "mitigation": "Restrict access to the affected add-on and review its access-control configuration to prevent user-controlled keys from granting unintended access. Upgrade to a vendor-provided fixed release when one is published.", "vendor": "WP E-Signature", "product": "Electronic Signature Add-on for Fluent Forms", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 2.0.5" ], "ecosystem": null, "fixed_versions": [], "package_name": "signature-fluent-contract-forms-add-on", "purl": null } ], "cwes": [ 639 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "epss_score": 0.003, "epss_percentile": 0.2184, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 28.090091, "t0_at": "2026-10-18T11:00:29.114000+00:00", "signals": { "check": { "at": "2026-10-18T12:35:17.684049+00:00", "days": 0.06583993112268519, "is_lower_bound": false, "measured_at": "2026-10-18T11:00:29.114000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-18T11:00:29.114000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-18T11:00:29.114000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-110383" } } }
published 2026-10-18 12:07Z
last change 2026-10-21 18:33Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.