Content Pilot - Security Vulnerability (CVE-2026-111070)

Q: Am I affected by this vulnerability?

You are affected if your site runs Content Pilot. No account is needed to exploit this, so a public site is reachable by anyone.

Q: How do I fix it?

Update Content Pilot to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.

CVE-2026-111070

Vulnerability CVE-2026-111070 PLUGIN content-pilot MEDIUM

The Content Pilot – Autoblogging & Affiliate Marketing Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.2.4. This is due to the plugin extracting the HTML meta description from each remotely-fetched article (WPCP_Readability::parse_meta()), piping that value through the article template substitution and html_entity_decode() in WPCP_Module::insert_post(), and then calling wp_insert_post() after switching the current user to the configured campaign author (an Administrator with the unfiltered_html capability by default) — so no wp_kses_post sanitization is applied to the attacker-controlled HTML before it is persisted as post_content and rendered on the front end. This makes it possible for unauthenticated attackers who control the content of any RSS source an administrator has configured a Content Pilot RSS campaign to consume to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVE-2026-111070

MEDIUM CVSS 5.4 Published 2026-10-31 Updated 2026-11-02

AI Risk Elevated (61/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority

Severity Band MEDIUM

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

Affected Components 2

Reference Links 7

AI Risk Engine Elevated (61/100)

Exploitability High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-10-31 CVE published and first recorded in the threat feed.
2026-11-02 Record updated with latest vulnerability metadata.
2026-11-07 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 4 days ago

AI enriched 4 days ago (2026-11-07 20:23 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 5.4). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 61/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Content Pilot PLUGIN · content-pilot Affected: <= 2.2.4 Fixed version not specified

Wp Content Pilot PLUGIN · wp-content-pilot Affected: <= 2.2.4 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Content Pilot to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Content Pilot, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?