Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2026-56005

WP Activity Log Cross-Site Scripting

Melapress / WP Activity Log · 0 to <= 5.6.3.1

View live feed Monitor via API Watch CVE-2026-56005
Severity
CVSS 7.1 · High
Confidence
High
Exploit status
Exploited in the wild
EPSS
0.3%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-56005 is an unauthenticated vulnerability affecting Melapress WP Activity Log. Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Melapress WP Activity Log...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Melapress / WP Activity Log 0 to <= 5.6.3.1.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

WP Activity Log Cross-Site Scripting

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Melapress WP Activity Log wp-security-audit-log allows Stored XSS.This issue affects WP Activity Log: from n/a through 5.6.3.1.

Melapress Affected
WP Activity Log wp-security-audit-log
Through 5.6.3.1
Published
25 Jun 2026
Exploitation Reported
02 Oct 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
Required

Tags

wordpress

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2026-56005
  • VDB Entry — patchstack.com patchstack.com · VDB Entry https://patchstack.com/database/wordpress/plugin/wp-security-audit-lo...

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 02 Oct 2026

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2026-10-02 06:40 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.1 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

0.3%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE-79

Timeline

From disclosure to observed exploitation

  1. 06:40 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 13:12 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 09:31 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-56005

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2026-56005",
  "confidence": "High",
  "cvss_score": 7.1,
  "cvss_estimated": false,
  "epss_score": 0.00251,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}