Finding and attribution
The rules publication path did not consistently require authentication or verify that the requesting user could see the board associated with a rule, allowing unauthorized publication of rules data. The fix checks authentication and board visibility.
Product: WeKan. AI system: AISLE AI analyzer (specific model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2026-2208.
AI and human contribution (source account): AISLE’s April 29, 2026 report states that its analyzer identified 24 WeKan CVEs, itemizes this case, and says the vulnerabilities were discovered by Joshua Rogers of AISLE. The exact model and division of work between the analyzer and researcher are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The CVE-specific AISLE record was published February 8, 2026; public campaign-level AI attribution appeared April 29, 2026. The patch is documented; no exploitation-in-the-wild claim is made.
Remediation status: fix documented. The WeKan patch adds authentication and board visibility checks for rules publications. Deployment status is not assessed.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 8 Feb 2026. AI attribution dated 29 Apr 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 5.3. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-2208: CVSS 4.0 · 5.3 (Medium) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X. VulDB (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-2208: CVSS 3.1 · 4.3 (Medium) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C. VulDB (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-2208: CVSS 3.0 · 4.3 (Medium) ·
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:X/RL:O/RC:C. VulDB (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-2208: CVSS 2.0 · 4 (Medium) ·
AV:N/AC:L/Au:S/C:P/I:N/A:N/E:ND/RL:OF/RC:C. VulDB (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-2208: other.
Prerequisites / affected scope: CNA states remote missing-authorization weakness in WeKan Rules Handler, but the protected object/data/action and resulting impact are not established in the description..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The WeKan patch adds authentication and board visibility checks for rules publications. Deployment status is not assessed.