How severe is CVE-2007-0418?

CVE-2007-0418 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2007-0418 being actively exploited?

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

What products are affected by CVE-2007-0418?

CVE-2007-0418 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-0418?

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

When was CVE-2007-0418 published?

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

CVE-2007-0418

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

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (73rd 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 SP6, 8.1 through 8.1 SP5, 9.0, and 9.1 does not enforce a security policy that declares permissions for EJB methods that have array parameters, which allows remote attackers to obtain unauthorized access to these methods.

Frequently asked questions

What is CVE-2007-0418?: BEA WebLogic Server 7.0 through 7.0 SP6, 8.1 through 8.1 SP5, 9.0, and 9.1 does not enforce a security policy that declares permissions for EJB methods that have array parameters, which allows remote attackers to obtain unauthorized access to these methods.
How severe is CVE-2007-0418?: CVE-2007-0418 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2007-0418 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-0418?: CVE-2007-0418 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-0418?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2007-0418 published?: CVE-2007-0418 was published on 2007-01-23 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:bea:weblogic_server:*:sp6:*:*:*:*:*:*
cpe:2.3:a:bea:weblogic_server:*:sp5:*:*:*:*:*:*
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: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-2007-0417 — Critical (CVSS 10.0): 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…
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…

All CVEs affecting Bea Weblogic Server →