CVE-2018-2463

HIGHNVD 8.68.6—Trending — 3 sources updated this week

8.6

The Omni Commerce Connect API (OCC) of SAP Hybris Commerce, versions 6.*, is vulnerable to server-side request forgery (SSRF) attacks. This is due to a misconfiguration of XML parser that is used in the server-side implementation of OCC.

CVSS v3: 8.6
EG Score: 8.6(medium)
EPSS: 51.8%
KEV: Not listed

Published

September 11, 2018

Last Modified

November 21, 2024

References (6)

cna@saphttp://www.securityfocus.com/bid/105339
cna@saphttps://launchpad.support.sap.com/#/notes/2680834
cna@saphttps://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=499356993
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/105339
af854a3a-2127-422b-91ae-364da2661108https://launchpad.support.sap.com/#/notes/2680834
af854a3a-2127-422b-91ae-364da2661108https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=499356993

Weakness Classification(1)

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

CWE-918Server-Side Request Forgery (SSRF)

Data Freshness Timeline

(refreshed 12× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 03:18 UTCEG score recompute
2026-05-28 03:18 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-2463?

CVE-2018-2463 is a high vulnerability published on September 11, 2018. The Omni Commerce Connect API (OCC) of SAP Hybris Commerce, versions 6.*, is vulnerable to server-side request forgery (SSRF) attacks. This is due to a misconfiguration of XML parser that is used in the server-side implementation of OCC.

When was CVE-2018-2463 disclosed?

CVE-2018-2463 was first published in the National Vulnerability Database on September 11, 2018, 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-2018-2463 actively exploited?

CVE-2018-2463 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-2463?

CVE-2018-2463 has a CVSS v3 base score of 8.6 (NVD).

How do I remediate CVE-2018-2463?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-2463, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-2463

Explore →

Is Your Infrastructure Affected by CVE-2018-2463?

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

Start Free Scan →Browse All CVEs

CVE-2018-2463

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-2463?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)