CVE-2023-36497

CVE-2023-36497 is a high-severity vulnerability in Doverfuelingsolutions Maglink Lx Web Console Configuration with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-305.

Key facts

Description

Dover Fueling Solutions MAGLINK LX Web Console Configuration versions 2.5.1, 2.5.2, 2.5.3, 2.6.1, 2.11, 3.0, 3.2, and 3.3 could allow a guest user to elevate to admin privileges.

Frequently asked questions

What is CVE-2023-36497?
Dover Fueling Solutions MAGLINK LX Web Console Configuration versions 2.5.1, 2.5.2, 2.5.3, 2.6.1, 2.11, 3.0, 3.2, and 3.3 could allow a guest user to elevate to admin privileges.
How severe is CVE-2023-36497?
CVE-2023-36497 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-36497 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-36497?
CVE-2023-36497 primarily affects Doverfuelingsolutions Maglink Lx Web Console Configuration. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2023-36497?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2023-36497 published?
CVE-2023-36497 was published on 2023-09-11 and last updated on 2026-06-17.

References

Affected products (8)

More vulnerabilities in Doverfuelingsolutions Maglink Lx Web Console Configuration

All CVEs affecting Doverfuelingsolutions Maglink Lx Web Console Configuration →

Other CWE-305 vulnerabilities

Browse all CWE-305 vulnerabilities →