Skip to content
Noroxi
CVE-2022-2034· NVD / CVE Program· CNA WPScan

Sensei LMS < 4.5.0 - Unauthenticated Private Messages Disclosure via Rest API

The Sensei LMS WordPress plugin before 4.5.0 does not have proper permissions set in one of its REST endpoint, allowing unauthenticated users to access private messages sent to teachers

MediumCVSS 5.3 · v3.1—Proof of concept No fix recorded
Published
Aug 29, 2022
Updated
Jun 17, 2026
EPSS
2.5% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

Affected systems

VendorProduct
automatticsensei lms

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • automattic sensei lmsbefore 4.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

  • Unknown Sensei LMS

    • before 4.5.0affected

Other highest-scoring records for the same primary product.

  • CVE-2024-7786Sensei LMS < 4.24.2 - Unauthenticated Email Template Leak
    22Monitor
  • CVE-2025-22740WordPress Sensei LMS plugin <= 4.24.4 - Broken Access Control vulnerability
    21Monitor
  • CVE-2025-0466Sensei LMS < 4.24.4 - Unauthenticated sensei_email/sensei_message Disclosure
    21Monitor
  • CVE-2024-35686WordPress Sensei LMS plugin <= 4.23.1 - Broken Access Control vulnerability
    21Monitor
  • CVE-2023-50875WordPress Sensei LMS Plugin <= 4.17.0 is vulnerable to Cross Site Scripting (XSS)
    21Monitor
  • CVE-2024-8009Sensei LMS < 4.20.0 - Teacher+ Users Email Address Disclosure
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2022-2034 —

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const invoice = await Invoice.findById(req.params.id);res.json(invoice);

Fixed

ts
const invoice = await Invoice.findOne({  id: req.params.id,  ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records