CVE-2023-5538

Mrpeng Mpoperationlogs cross-site scripting (XSS)

7.2 HIGHPublic exploitEPSS 0.98%

Published18 Oct 2023

Description

The MpOperationLogs plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the IP Request Headers in versions up to, and including, 1.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityLow

IntegrityLow

AvailabilityNone

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

Affected products

Mrpeng Mpoperationlogs≤ 1.0.1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/juweihuitao/MpOperationLogs/ExploitThird Party Advisory
https://plugins.trac.wordpress.org/browser/mpoperationlogs/trunk/common.php#L10Product
https://plugins.trac.wordpress.org/browser/mpoperationlogs/trunk/template/ipslist_td.phpProduct
https://www.wordfence.com/threat-intel/vulnerabilities/id/bc5f1b00-acee-4dc8-acd7-2d3f3493f253?source=cveExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2023-5538 being actively exploited?

CVE-2023-5538 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.98%.

How severe is CVE-2023-5538?

CVE-2023-5538 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 0.98% probability of exploitation.

Which products are affected by CVE-2023-5538?

Affected products include Mrpeng Mpoperationlogs.

How do I fix CVE-2023-5538?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-5538 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.