Wowza Streaming Engine before 4.8.8.01 (in a default installation) has cleartext passwords stored in the conf/admin.password file.

published 2021-04-23 5y ago modified 2026-06-17 4mo ago also EUVD-2021-18437

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits: 0; none known

Wowza Streaming Engine before 4.8.8.01 (in a default installation) has cleartext passwords stored in the conf/admin.password file. A regular local user is able to read usernames and passwords.

Patch / fix

fixed in 1

wowza streaming_engine 4.8.8.01

Is CVE-2021-31539 in your stack? 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

Exploit prediction

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

Exploits and checks

gruppotim.it https://www.gruppotim.it/redteam referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-312 Cleartext Storage of Sensitive Information

References

gruppotim.it /redteam
exploit, third-party-advisory
wowza.com /products/streaming-engine
product, vendor-advisory
wowza.com /docs/wowza-streaming-engine-4-8-8-01-release-notes#breaking
release-notes, vendor-advisory

Sources

CVE List CVE-2021-31539
NVD CVE-2021-31539

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.