CVE-2013-4810

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Exploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 79%CVSS: 9.8Exploit: cisa kev · ssvc active · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

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

HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, Identity Driven Manager (IDM) 4.0, and Application Lifecycle Management allow remote attackers to execute arbitrary code via a marshalled object to (1) EJBInvokerServlet or (2) JMXInvokerServlet, aka ZDI-CAN-1760. NOTE: this is probably a duplicate of CVE-2007-1036, CVE-2010-0738, and/or CVE-2012-0874.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100CISA SSVC

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%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
79%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2013

Last Modified

April 21, 2026

Advisory Details (6)

Auto-updated Oct 1, 2026
🔬 Proof of concept available. No fix on record yet.
generic

'[security bulletin] HPSBGN03323 rev.1 - HP Business Service Automation Essentials Core with JBOSS, R' - MARC

http://marc.info/?l=bugtraq&m=143039425503668&w=2
generic

'[security bulletin] HPSBGN02952 rev.1 - HP Application Lifecycle Manager (ALM) Running JBoss Applica' - MARC

http://marc.info/?l=bugtraq&m=138696448823753&w=2
generic🟡 PoC Available

Apache Tomcat/JBoss EJBInvokerServlet / JMXInvokerServlet (RMI over HTTP) Marshalled Object - Remote Code Execution - PHP remote Exploit

https://www.exploit-db.com/exploits/28713/
generic

ZDI-13-229 - TrendAI™ Zero Day Initiative™ (ZDI)

http://zerodayinitiative.com/advisories/ZDI-13-229/
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/54788

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 44× in last 7d / 211× 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.

Showing the most recent 100 of 917 total refreshes for this CVE.

  1. 2026-10-06 06:38 UTCGHSA enrichment
  2. 2026-10-06 02:31 UTCGHSA enrichment
  3. 2026-10-05 22:25 UTCGHSA enrichment
  4. 2026-10-05 18:18 UTCGHSA enrichment
  5. 2026-10-05 14:13 UTCGHSA enrichment
  6. 2026-10-05 10:07 UTCGHSA enrichment
  7. 2026-10-05 06:01 UTCGHSA enrichment
  8. 2026-10-05 01:55 UTCGHSA enrichment
  9. 2026-10-04 21:49 UTCGHSA enrichment
  10. 2026-10-04 17:44 UTCGHSA enrichment
  11. 2026-10-04 13:37 UTCGHSA enrichment
  12. 2026-10-04 09:32 UTCGHSA enrichment
  13. 2026-10-04 05:26 UTCGHSA enrichment
  14. 2026-10-04 01:21 UTCGHSA enrichment
  15. 2026-10-03 21:16 UTCGHSA enrichment
  16. 2026-10-03 17:10 UTCGHSA enrichment
  17. 2026-10-03 13:00 UTCGHSA enrichment
  18. 2026-10-03 08:52 UTCGHSA enrichment
  19. 2026-10-03 04:47 UTCGHSA enrichment
  20. 2026-10-03 00:41 UTCGHSA enrichment
  21. 2026-10-02 20:35 UTCGHSA enrichment
  22. 2026-10-02 16:26 UTCGHSA enrichment
  23. 2026-10-02 16:25 UTCGHSA enrichment
  24. 2026-10-02 12:19 UTCGHSA enrichment
  25. 2026-10-02 08:13 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 04:06 UTCGHSA enrichment
  2. 2026-10-01 23:59 UTCGHSA enrichment
  3. 2026-10-01 19:54 UTCEG score recompute
  4. 2026-10-01 19:54 UTCGHSA enrichment
  5. 2026-10-01 15:48 UTCGHSA enrichment
  6. 2026-10-01 11:42 UTCGHSA enrichment
  7. 2026-10-01 07:34 UTCGHSA enrichment
  8. 2026-10-01 03:28 UTCGHSA enrichment
  9. 2026-09-30 23:23 UTCGHSA enrichment
  10. 2026-09-30 19:15 UTCGHSA enrichment
  11. 2026-09-30 15:10 UTCGHSA enrichment
  12. 2026-09-30 11:04 UTCGHSA enrichment
  13. 2026-09-30 06:59 UTCGHSA enrichment
  14. 2026-09-30 02:53 UTCGHSA enrichment
  15. 2026-09-29 22:47 UTCGHSA enrichment
  16. 2026-09-29 18:39 UTCEG score recompute
  17. 2026-09-29 18:38 UTCGHSA enrichment
  18. 2026-09-29 14:30 UTCGHSA enrichment
  19. 2026-09-29 10:24 UTCGHSA enrichment
  20. 2026-09-29 06:16 UTCGHSA enrichment
  21. 2026-09-29 02:11 UTCGHSA enrichment
  22. 2026-09-28 22:05 UTCEG score recompute
  23. 2026-09-28 22:05 UTCGHSA enrichment
  24. 2026-09-28 17:59 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCGHSA enrichment
  26. 2026-09-28 09:46 UTCGHSA enrichment
  27. 2026-09-28 05:41 UTCGHSA enrichment
  28. 2026-09-28 01:35 UTCGHSA enrichment
  29. 2026-09-27 21:51 UTCCISA KEV update
  30. 2026-09-27 21:29 UTCGHSA enrichment
  31. 2026-09-27 17:21 UTCGHSA enrichment
  32. 2026-09-27 13:16 UTCGHSA enrichment
  33. 2026-09-27 09:10 UTCGHSA enrichment
  34. 2026-09-27 05:03 UTCGHSA enrichment
  35. 2026-09-27 00:58 UTCGHSA enrichment
  36. 2026-09-26 20:52 UTCGHSA enrichment
  37. 2026-09-26 16:46 UTCGHSA enrichment
  38. 2026-09-26 12:38 UTCGHSA enrichment
  39. 2026-09-26 08:31 UTCGHSA enrichment
  40. 2026-09-26 04:22 UTCGHSA enrichment
  41. 2026-09-26 00:16 UTCGHSA enrichment
  42. 2026-09-25 20:10 UTCGHSA enrichment
  43. 2026-09-25 19:35 UTCCISA KEV update
  44. 2026-09-25 16:01 UTCGHSA enrichment
  45. 2026-09-25 14:55 UTCCISA KEV update
  46. 2026-09-25 11:56 UTCGHSA enrichment
  47. 2026-09-25 07:50 UTCGHSA enrichment
  48. 2026-09-25 03:45 UTCGHSA enrichment
  49. 2026-09-24 23:39 UTCGHSA enrichment
  50. 2026-09-24 19:34 UTCGHSA enrichment
  51. 2026-09-24 19:31 UTCCISA KEV update
  52. 2026-09-24 15:28 UTCEG score recompute
  53. 2026-09-24 15:28 UTCGHSA enrichment
  54. 2026-09-24 11:23 UTCGHSA enrichment
  55. 2026-09-24 07:17 UTCGHSA enrichment
  56. 2026-09-24 03:12 UTCGHSA enrichment
  57. 2026-09-23 23:07 UTCGHSA enrichment
  58. 2026-09-23 19:01 UTCGHSA enrichment
  59. 2026-09-23 14:55 UTCGHSA enrichment
  60. 2026-09-23 10:50 UTCGHSA enrichment
  61. 2026-09-23 06:44 UTCGHSA enrichment
  62. 2026-09-23 02:39 UTCGHSA enrichment
  63. 2026-09-22 22:33 UTCGHSA enrichment
  64. 2026-09-22 19:36 UTCCISA KEV update
  65. 2026-09-22 18:27 UTCEG score recompute
  66. 2026-09-22 18:27 UTCGHSA enrichment
  67. 2026-09-22 14:21 UTCGHSA enrichment
  68. 2026-09-22 10:15 UTCGHSA enrichment
  69. 2026-09-22 06:09 UTCGHSA enrichment
  70. 2026-09-22 02:03 UTCGHSA enrichment
  71. 2026-09-21 21:58 UTCEG score recompute
  72. 2026-09-21 21:58 UTCGHSA enrichment
  73. 2026-09-21 20:25 UTCEPSS rescore
  74. 2026-09-21 19:09 UTCCISA KEV update
  75. 2026-09-21 17:52 UTCGHSA enrichment

Publicly available exploits

(1 reference)

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-28713✓ verified
    First seen Oct 4, 2013

    Apache Tomcat/JBoss EJBInvokerServlet / JMXInvokerServlet (RMI over HTTP) Marshalled Object - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2013-4810?
CVE-2013-4810 is a critical vulnerability published on September 16, 2013. HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, Identity Driven Manager (IDM) 4.0, and Application Lifecycle Management allow remote attackers to execute arbitrary code via a marshalled object to (1) EJBInvokerServlet or (2) JMXInvokerServlet, aka ZDI-CAN-1760. NOTE: this is probably a…
When was CVE-2013-4810 disclosed?
CVE-2013-4810 was first published on September 16, 2013, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4810 actively exploited?
Yes. CISA added CVE-2013-4810 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Hewlett Packard (HP) ProCurve Manager (PCM), PCM+, Identity Driven Manager (IDM), and Application Lifecycle Management. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2013-4810?
CVE-2013-4810 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2013-4810?
CVE-2013-4810 affects Hewlett Packard (HP) ProCurve Manager (PCM), PCM+, Identity Driven Manager (IDM), and Application Lifecycle Management.
How do I remediate CVE-2013-4810?
No fix for CVE-2013-4810 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-4810

Explore →

Is Your Infrastructure Affected by CVE-2013-4810?

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