Skip to main content
VulnerabilityPublished

CVE-2026-14826: Quiz and Survey Master (QSM) (WordPress plugin) · Insecure Direct Object Reference

Affects Quiz and Survey Master (QSM) (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 11.2.4 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.2.4
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Upgrade Quiz and Survey Master (QSM) (WordPress plugin) to 11.2.4.

Affected software

ProductAffectedFixed in
Quiz and Survey Master (QSM)Affected
  • <11.2.4
Fixed in
  • 11.2.4

AI-suggested

Upgrade the Quiz and Survey Master (QSM) plugin to version 11.2.4 or later, where this authorization bypass vulnerability has been fixed. No other mitigation is necessary once the plugin is updated.

Description

A vulnerability in the Quiz and Survey Master (QSM) WordPress plugin before version 11.2.4 allows users with contributor-level access and above to bypass authorization checks on certain REST API routes. This flaw permits these users to read email-notification and results-page configurations of quizzes created by other users, potentially exposing notification recipient addresses. The issue is due to missing per-object ownership verification on these REST endpoints.

References

Community reviews

Loading reviews…