Skip to main content
Mallory
MediumVulnerability

CVE-2013-4625: XSS in Duplicator WordPress Plugin (installer.cleanup.php)

Published Aug 9, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS11.1%96th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Cory Lamle
IdentifiersCVE-2013-4625CWE-79 · Improper Neutralization of Input…

A cross-site scripting (XSS) vulnerability exists in the Duplicator plugin for WordPress prior to version 0.4.5. The vulnerability is present in the files/installer.cleanup.php script, where the 'package' parameter is not properly sanitized, allowing remote attackers to inject arbitrary web script or HTML.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary JavaScript in the context of the victim's browser session, potentially leading to session hijacking, credential theft, or other attacks leveraging the user's authenticated state in WordPress.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict access to the installer.cleanup.php file via web server configuration or .htaccess rules, and ensure that user-supplied input is not reflected in responses without proper sanitization and encoding.

Remediation

Patch, then assume compromise.

Upgrade the Duplicator plugin to version 0.4.5 or later, where the input validation and output encoding for the 'package' parameter in installer.cleanup.php have been corrected to prevent XSS.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cory LamleDuplicatorapplication
FAQ

Frequently asked questions

Is CVE-2013-4625 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-4625 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-4625?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2013-4625. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2013-4625?
Upgrade the Duplicator plugin to version 0.4.5 or later, where the input validation and output encoding for the 'package' parameter in installer.cleanup.php have been corrected to prevent XSS.
What products are affected by CVE-2013-4625?
Cory Lamle Duplicator.
How severe is CVE-2013-4625?
CVE-2013-4625 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 11.1% (96th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.