How severe is CVE-2007-0417?

CVE-2007-0417 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2007-0417 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-0417?

CVE-2007-0417 primarily affects Bea Weblogic Server. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2007-0417?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2007-0417 published?

CVE-2007-0417 was published on 2007-01-23 and last updated on 2026-06-16.

CVE-2007-0417

CVE-2007-0417 is a critical-severity vulnerability in Bea Weblogic Server with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Bea Weblogic Server
Published: 2007-01-23
Last modified: 2026-06-16

Description

BEA WebLogic Server 7.0 through 7.0 SP7, 8.1 through 8.1 SP5, 9.0, and 9.1, when using the WebLogic Server 6.1 compatibility realm, allows attackers to execute certain EJB container persistence operations with an administrative identity.

Frequently asked questions

What is CVE-2007-0417?: BEA WebLogic Server 7.0 through 7.0 SP7, 8.1 through 8.1 SP5, 9.0, and 9.1, when using the WebLogic Server 6.1 compatibility realm, allows attackers to execute certain EJB container persistence operations with an administrative identity.
How severe is CVE-2007-0417?: CVE-2007-0417 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2007-0417 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-0417?: CVE-2007-0417 primarily affects Bea Weblogic Server. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2007-0417?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2007-0417 published?: CVE-2007-0417 was published on 2007-01-23 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:bea:weblogic_server:*:sp7:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:7.0:*:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:8.1:*:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:8.1:sp5:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:9.0:*:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:9.1:*:*:*:*:*:*:*

More vulnerabilities in Bea Weblogic Server

CVE-2008-3257 — Critical (CVSS 10.0): Stack-based buffer overflow in the Apache Connector (mod_wl) in Oracle WebLogic Server (formerly BEA WebLogic Server)…
CVE-2003-0640 — Critical (CVSS 10.0): BEA WebLogic Server and Express, when using NodeManager to start servers, provides Operator users with privileges to…
CVE-2001-0098 — Critical (CVSS 10.0): Buffer overflow in Bea WebLogic Server before 5.1.0 allows remote attackers to execute arbitrary commands via a long…
CVE-2000-0684 — Critical (CVSS 10.0): BEA WebLogic 5.1.x does not properly restrict access to the JSPServlet, which could allow remote attackers to compile…
CVE-2000-0681 — Critical (CVSS 10.0): Buffer overflow in BEA WebLogic server proxy plugin allows remote attackers to execute arbitrary commands via a long…
CVE-2000-0685 — Critical (CVSS 10.0): BEA WebLogic 5.1.x does not properly restrict access to the PageCompileServlet, which could allow remote attackers to…

All CVEs affecting Bea Weblogic Server →