CVE-2019-5434

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 57%
CISA-KEV: Not listedEPSS: 57%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
71(Track*)
EG Risk 71/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation57% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.0%
KEV
Not listed

Published

May 6, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

Revive Adserver Security Advisory SA-2019-001

https://www.revive-adserver.com/security/revive-sa-2019-001/
generic

HackerOne

https://hackerone.com/reports/542670
generic

HackerOne

https://hackerone.com/reports/512076

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 01:45 UTCEG score recompute
  3. 2026-07-22 22:27 UTCEG score recompute
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 02:26 UTCEPSS rescore
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:55 UTCEPSS rescore
  11. 2026-07-15 01:57 UTCEPSS rescore
  12. 2026-07-13 06:10 UTCEPSS rescore
  13. 2026-07-13 06:10 UTCEPSS rescore
  14. 2026-07-12 05:44 UTCEPSS rescore
  15. 2026-07-12 05:43 UTCEPSS rescore
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-11 08:24 UTCEPSS rescore
  18. 2026-07-09 19:06 UTCEPSS rescore
  19. 2026-07-07 13:43 UTCEPSS rescore
  20. 2026-07-06 16:25 UTCEPSS rescore
  21. 2026-07-06 16:25 UTCEPSS rescore
  22. 2026-07-05 02:27 UTCEPSS rescore
  23. 2026-07-01 15:03 UTCEPSS rescore
  24. 2026-07-01 15:03 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
Show 31 more
  1. 2026-06-28 04:54 UTCEPSS rescore
  2. 2026-06-28 04:54 UTCEPSS rescore
  3. 2026-06-27 03:06 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-19 19:23 UTCEPSS rescore
  11. 2026-06-19 19:23 UTCEPSS rescore
  12. 2026-06-18 17:50 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-17 17:50 UTCEPSS rescore
  15. 2026-06-16 17:50 UTCEPSS rescore
  16. 2026-06-15 17:46 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-10 22:16 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-05 22:45 UTCEPSS rescore
  23. 2026-06-02 20:11 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-01 13:50 UTCEPSS rescore
  26. 2026-06-01 13:50 UTCEPSS rescore
  27. 2026-05-28 13:43 UTCEPSS rescore
  28. 2026-05-28 13:43 UTCEPSS rescore
  29. 2026-05-27 19:53 UTCEG score recompute
  30. 2026-05-27 19:53 UTCGHSA enrichment
  31. 2026-05-24 16:47 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47739
    First seen Dec 3, 2019

    Revive Adserver 4.2 - Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-5434.yaml
    First seen Jan 1, 2019

    Revive Adserver 4.2 - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-5434?
CVE-2019-5434 is a critical vulnerability published on May 6, 2019. 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…
When was CVE-2019-5434 disclosed?
CVE-2019-5434 was first published in the National Vulnerability Database on May 6, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-5434 actively exploited?
CVE-2019-5434 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-5434?
CVE-2019-5434 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-5434?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-5434, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-5434

Explore →

Is Your Infrastructure Affected by CVE-2019-5434?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs