Skip to main content
VulnerabilityPublished

CVE-2026-41243: siemvk OpenLearn · Improper Access Control

Affects siemvk OpenLearnSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
siemvkOpenLearnAffected
  • =< 844b2a40a69d0c4911580fe501923f0b391313ab
Fixed in–

AI-suggested

The vulnerability is fixed in commit 844b2a40a69d0c4911580fe501923f0b391313ab. Users of OpenLearn should update to this commit or a later version that includes this fix. No official vendor advisory or patch link is provided, so users should verify the fix in the project repository.

Description

CVE-2026-41243 is an improper access control vulnerability in the open-source forum software OpenLearn by siemvk. Before a specific code commit (844b2a40a69d0c4911580fe501923f0b391313ab), when safeMode was enabled, unapproved forum posts were hidden from public listings but could still be accessed directly by anyone with the post UUID. This allowed unauthorized users to read posts that should have been restricted. The issue was fixed in the referenced commit.

References

Community reviews

Loading reviews…