Menu

Star on GitHub · 3.2k

CVE-1999-0890

7.5 · HIGH

iHTML Merchant allows remote attackers to obtain sensitive information or execute commands via a code parsing error.

Published Sep 16, 1999ihtml_merchantEPSS 1.88%

Overview

CVE-1999-0890 is a high-severity vulnerability affecting ihtml_merchant ihtml_merchant. It was published on September 16, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

iHTML Merchant allows remote attackers to obtain sensitive information or execute commands via a code parsing error.

Remediation

Check the references section for vendor advisories and patches from ihtml_merchant. Update ihtml_merchant 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

VendorProductVersionsStatus

Frequently asked questions

What is CVE-1999-0890?

CVE-1999-0890 is a high-severity vulnerability affecting ihtml_merchant ihtml_merchant. It was published on September 16, 1999 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-1999-0890?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-1999-0890?

Check the references section for vendor advisories and patches from ihtml_merchant. Update ihtml_merchant 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-1999-0890?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-1999-0890 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.