dbcve.org
Weblogic ServerApplication · Bea

CVE-2005-1747

MEDIUM · 6.8 CVSS v2.0 Published 2005-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple cross-site scripting (XSS) vulnerabilities in BEA WebLogic Server and Express versions 8.1 (through SP4) and 7.0 (through SP6) allow remote attackers to inject arbitrary web script or HTML via j_username and j_password parameters on the login page (LoginForm.jsp), error pages in the Administration Console, and Server Console vectors. Successful exploitation can lead to session hijacking and administrative privilege escalation.

MitigationUpgrade to a patched WebLogic version beyond Service Pack 4 (8.1) and Service Pack 6 (7.0), or apply vendor-supplied security patches; implement input validation and output encoding on all user-supplied parameters as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Weblogic ServerApplication
Affected:= 6.0= 6.1= 7.0= 7.0.0.1= 8.1
Weblogic PortalApplication
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WebLogic Server version
    Run 'java -jar weblogic.jar' or check the BEA_HOME directory for version files, or inspect the runtime version via the Administration Console
    Affected if The version is 6.0, 6.1, 7.0, 7.0.0.1, or 8.1 (SP4 or earlier)
  2. Confirm WebLogic Portal version if applicable
    Check the Oracle Weblogic Portal installation directory for version metadata or inspect the portal runtime configuration
    Affected if Version 8.0 is installed
  3. Verify Administration Console is accessible
    Attempt to access the WebLogic Administration Console via HTTP/HTTPS on the configured admin port (default 7001)
    Affected if The Administration Console is reachable and no output encoding is applied to error messages
  4. Check LoginForm.jsp for parameter handling
    Access the login page (typically at /console/login/LoginForm.jsp) and inspect whether j_username and j_password parameters are reflected in the response without sanitization
    Affected if User input in j_username or j_password is echoed back unencoded in the HTML response

Your environment is affected if you are running WebLogic Server 6.0 through 8.1 (SP4 or earlier) or WebLogic Portal 8.0, and the Administration Console or login form is accessible over the network with unvalidated parameter handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched WebLogic version beyond Service Pack 4 (8.1) and Service Pack 6 (7.0), or apply vendor-supplied security patches; implement input validation and output encoding on all user-supplied parameters as a compensating control.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-1747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-1747 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data