CVE-2026-4375
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe DoLeads Integrator WordPress plugin through 0.65, wp2epub WordPress plugin through 0.65 have been seen to be used to achieve RCE, once they are added adding to a blog, for example using a vulnerability where unclosed extensions from wordpress.org can be installed by unauthorized users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe DoLeads Integrator and wp2epub WordPress plugins (versions up to 0.65) contain a vulnerability allowing unauthorized installation of extensions from wordpress.org, which has been exploited to achieve Remote Code Execution (RCE). The specific vulnerability mechanism is not detailed, but the CVSS 9 score indicates a critical severity flaw allowing full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if DoLeads Integrator plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for a folder named 'doleads-integrator' or similar. Check the plugin header for version number.Affected if Plugin is present and version is 0.65 or lower
-
Check if wp2epub plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for a folder named 'wp2epub'. Check the plugin header for version number.Affected if Plugin is present and version is 0.65 or lower
-
Verify plugin versions against affected rangeCompare installed plugin versions to the affected range (any version up to and including 0.65). Check plugin readme.txt or main PHP file for exact version string.Affected if Installed version is 0.65 or any earlier version
-
Look for unauthorized plugin installationsReview all plugins in /wp-content/plugins/ directory. Check WordPress activity log or server access logs for requests to wordpress.org plugin installation API originating from the site.Affected if New plugins exist that were not intentionally installed by administrators
-
Inspect for backdoor or malicious code indicatorsReview recently modified PHP files in /wp-content/plugins/ directory and /wp-content/ theme files. Check for suspicious eval(), base64_decode(), or shell execution functions.Affected if Unexpected code changes or suspicious functions are found in plugin or theme files
Users are affected if either DoLeads Integrator or wp2epub plugin is installed with version 0.65 or lower, or if unauthorized extensions appear to have been installed on the WordPress site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove both DoLeads Integrator and wp2epub plugins immediately if installed, as they have known RCE exploits; conduct a full compromise assessment of affected WordPress installations to check for existing backdoors or malicious code planted through this attack vector.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data