Skip to content
Fencer Intel
critical 9.8

CVE-2019-5434 in the critical feed json

An attacker could send a specifically crafted payload to the XML-RPC invocation script and trigger the unserialize() call on the "what" par…

published 7y ago modified 4mo ago also EUVD-2019-15024

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
57.0%
EPSS 57.0% chance of exploitation in 30 days, percentile 99%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

An attacker could send a specifically crafted payload to the XML-RPC invocation script and trigger the unserialize() call on the "what" parameter in the "openads.spc" RPC method. Such vulnerability could be used to perform various types of attacks, e.g. exploit serialize-related PHP vulnerabilities or PHP object injection. It is possible, although unconfirmed, that the vulnerability has been used by some attackers in order to gain access to some Revive Adserver instances and deliver malware through them to third party websites. This vulnerability was addressed in version 4.2.0.

Patch / fix

  • revive-sas revive_adserver 4.2.0

Is CVE-2019-5434 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

Timeline

  1. Published
  2. First public exploit (EDB-47739)

Exploit prediction

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

Exploits and checks

  • EDB-47739 Revive Adserver 4.2 - Remote Code Execution webapps, 2019-12-03
  • Nuclei template Revive Adserver 4.2 - Remote Code Execution nuclei detection template

CVSS scores

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

Affected products

  • n/a Revive Adserver

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

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.