Skip to content
WatchlistHigh

CVE-2018-7582Weblog Expert Vulnerability

WebLog Expert Web Server Enterprise 9.4 allows Remote Denial Of Service (daemon crash) via a long HTTP Accept Header to TCP port 9991.

Published Mar 9, 2018 · Updated Nov 21, 2024

Key Facts

Patch immediately
  • CVE-2018-7582 is a high-severity vulnerability (CVSS 7.5 v3) affecting Weblog Expert (Weblogexpert).
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 36% probability of exploitation in the next 30 days.
  • No fixed version is listed yet; check the vendor advisory for mitigations.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v3

7.5

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

EPSS (30-day exploit likelihood)

36%

Higher than 98.4% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

43/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

3

Proof-of-concept links

In-the-wild evidence

1

Reports of active use

Description

WebLog Expert Web Server Enterprise 9.4 allows Remote Denial Of Service (daemon crash) via a long HTTP Accept Header to TCP port 9991.

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
Weblog ExpertWeblogexpert9.4n/a

Timeline

  1. Publicly disclosed

    Mar 9, 2018

  2. Last updated

    Nov 21, 2024

Weakness Type

  • CWE-770 Allocation of Resources Without Limits or Throttling

FAQ

Common Questions.

Is CVE-2018-7582 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.