CVE-2005-1747
6.8 · MEDIUMOverview
CVE-2005-1747 is a medium-severity vulnerability affecting bea weblogic_server. It was published on May 24, 2005 and has a CVSS 2.0 base score of 6.8 (MEDIUM).
This vulnerability has a CVSS 2.0 base score of 6.8, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
Multiple cross-site scripting (XSS) vulnerabilities in BEA WebLogic Server and Express 8.1 through Service Pack 4, and 7.0 through Service Pack 6, allow remote attackers to inject arbitrary web script or HTML, and possibly gain administrative privileges, via the (1) j_username or (2) j_password parameters in the login page (LoginForm.jsp), (3) parameters to the error page in the Administration Console, (4) unknown vectors in the Server Console while the administrator has an active session to obtain the ADMINCONSOLESESSION cookie, or (5) an alternate vector in the Server Console that does not require an active session but also leaks the username and password.
Remediation
Check the references section for vendor advisories and patches from bea. Update weblogic_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2005-1747?
CVE-2005-1747 is a medium-severity vulnerability affecting bea weblogic_server. It was published on May 24, 2005 and has a CVSS 2.0 base score of 6.8 (MEDIUM).
How severe is CVE-2005-1747?
This vulnerability has a CVSS 2.0 base score of 6.8, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2005-1747?
Check the references section for vendor advisories and patches from bea. Update weblogic_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2005-1747?
CyberStrike's AI-powered security agents can automatically detect CVE-2005-1747 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2005
View all →Race condition in the Radeon DRI driver for Linux kernel 2.6.8.1 allows local users with DRI privile
Race condition in the page fault handler (fault.c) for Linux kernel 2.2.x to 2.2.7, 2.4 to 2.4.29, a
Multiple untrusted search path vulnerabilities in SUSE Linux 9.3 and 10.0, and possibly other distri
Cross-site scripting (XSS) vulnerability in standard_error_message.dtml for Zwiki after 0.10.0rc1 to
Cross-site scripting (XSS) vulnerability in mailpost.exe in MailPost 5.1.1sv, and possibly earlier v
Cross-site scripting (XSS) vulnerability in Gallery 1.4.4-pl3 and earlier allows remote attackers to
Cross-site scripting (XSS) vulnerability in admin.asp in CMailServer 5.2 allows remote attackers to
Multiple cross-site scripting (XSS) vulnerabilities in Microsoft W3Who ISAPI (w3who.dll) allow remot
Cross-site scripting (XSS) vulnerability in inmail.pl in Insite Inmail allows remote attackers to in
Cross-site scripting (XSS) vulnerability in inshop.pl in Insite inShop allows remote attackers to in
Cross-site scripting (XSS) vulnerability in parser.php in phpCMS 1.2.1 and earlier, with non-stealth
Cross-site scripting (XSS) vulnerability in proxylog.dat in IPCop 1.4.1 and possibly other versions,