Skip to content
Fencer Intel
high 7.6

CVE-2022-4068 in the critical feed json

Improperly Controlled Modification of Dynamically-Determined Object Attributes in librenms/librenms

published 3y ago modified 4mo ago also GHSA-f3hw-3h74-wr98 , EUVD-2022-7322

cvss
7.6
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
37.5%
EPSS 37.5% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

A user is able to enable their own account if it was disabled by an admin while the user still holds a valid session. Moreover, the username is not properly sanitized in the admin user overview. This enables an XSS attack that enables an attacker with a low privilege user to execute arbitrary JavaScript in the context of an admin's account.

Patch / fix

  • packagist librenms/librenms 22.10.0
  • librenms librenms/librenms 22.10.0

Is CVE-2022-4068 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

37.55% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/becfecc4-22a6-4f94-bf83-d6030b625fdc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.6 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
GitHub 3.0 7.6 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
packagist librenms/librenms
<22.10.0
22.10.0

Affected products

  • librenms librenms/librenms

Classification

Weakness
  • CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.