dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-23733

HIGH · 7.5 CVSS v3.1 Published 2025-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
The /WmAdmin/,/invoke/vm.server/login login page in the Integration Server in Software AG webMethods 10.15.0 before Core_Fix7 allows remote attackers to reach the administration panel and discover hostname and version information by sending an arbitrary username and a blank password to the /WmAdmin/#/login/ URI.

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

The Integration Server's /WmAdmin login page in Software AG webMethods 10.15.0 before Core_Fix7 contains an authentication bypass vulnerability allowing remote unauthenticated attackers to access the admin panel by providing any username with a blank password. This enables disclosure of sensitive system information including hostname and software version details.

MitigationApply Software AG Core_Fix7 for webMethods 10.15.0 or later. As an interim measure, restrict network access to the /WmAdmin/ endpoint using firewall rules or network segmentation to prevent unauthorized external access.

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

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Verify the webMethods Integration Server version
    Locate the Software AG installation directory and check the version file or use the 'sagcc get versions' command if the command center is available. Look for the build number or fix level (Core_Fix number).
    Affected if The version is 10.15.0 and the installed fix level is before Core_Fix7 (or the fix level cannot be determined and the version is 10.15.0).
  2. Confirm the /WmAdmin endpoint is network accessible
    Attempt to reach the /WmAdmin path on the Integration Server over HTTP or HTTPS (for example, http://hostname:port/WmAdmin or https://hostname:port/WmAdmin). A successful connection returns the login page.
    Affected if The /WmAdmin login page loads and is reachable from the network being tested.
  3. Test for the blank password authentication bypass
    On the /WmAdmin login page, enter any username (for example, 'admin') and leave the password field empty, then submit the login request. Observe whether access is granted to the admin panel.
    Affected if The login succeeds with any username and a blank password, exposing the admin dashboard and system information.

You are affected if your webMethods Integration Server is version 10.15.0 without Core_Fix7 applied, the /WmAdmin endpoint is network-accessible, and a login with a blank password grants access to the admin panel.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Software AG Core_Fix7 for webMethods 10.15.0 or later. As an interim measure, restrict network access to the /WmAdmin/ endpoint using firewall rules or network segmentation to prevent unauthorized external access.

Recommended fix Moderate confidence

Software AG webMethods 10.15.0 with Core_Fix7

  1. Verify current webMethods Integration Server version using the SAGDesigner or admin console
  2. Apply Software AG Core_Fix7 for webMethods 10.15.0, available through Software AG Empower portal or official support channels
  3. After applying the fix, verify that blank passwords are no longer accepted on /WmAdmin/ and /invoke/vm.server/login endpoints
  4. Confirm the login page now properly rejects authentication attempts with blank passwords

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23733 — 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-2024-23733 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