VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 2 known issues Latest disclosed Sep 26, 2017

Content Audit Vulnerabilities

Review known vulnerability records for the WordPress plugin Content Audit (`content-audit`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2017-18560 and CVE-2014-5389, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
2
High or Critical
1
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing Content Audit fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Content Audit remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
2
1. Match the Package
Confirm the installed WordPress plugin slug is content-audit before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
2 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2014-5389 High
SQL Injection remediation for Content Audit

Affected range: Versions before 1.6.1. Fixed version: 1.6.1.

CVE-2017-18560 Medium
Cross-Site Scripting remediation for Content Audit

Affected range: Versions up to 1.9.1. Fixed version: 1.9.2.

Priority CVE Quick Links

Fast paths into Content Audit CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
2
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2014-5389
Content Audit <= 1.6.0 - Authenticated (Admin+) SQL Injection
 SQL Injection Versions before 1.6.1 1.6.1 CVSS 7.2
CVE-2017-18560
Content Audit <= 1.9.1 - Cross-Site Request Forgery to Cross-Site Scripting
 Cross-Site Scripting Versions up to 1.9.1 1.9.2 CVSS 6.1
CVE-2014-5389 High 1.6.1
CVE-2014-5389 Content Audit SQL Injection

Content Audit <= 1.6.0 - Authenticated (Admin+) SQL Injection

CVE-2017-18560 Medium 1.9.2
CVE-2017-18560 Content Audit Cross-Site Scripting

Content Audit <= 1.9.1 - Cross-Site Request Forgery to Cross-Site Scripting

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Content Audit so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
2 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2017-18560 and CVE-2014-5389
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Content Audit

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2017-18560
CVE-2017-18560: Content Audit <= 1.9.1 - Cross-Site Request Forgery to Cross-Site Scripting

The Content Audit plugin for WordPress is vulnerable to Cross-Site Request Forgery via the content_audit_save_bulk_edit AJAX action which allows for stored XSS payloads in versions up to, and including, 1.9.1 due to insufficient input sanitization and output escaping. This makes...

Published
Sep 26, 2017
Patched Release
1.9.2
Affected Versions
Versions up to 1.9.1
Next Step
Update to 1.9.2 or newer if supported.
Review CVE-2017-18560 fixed version details Open CVE Reference
Plugin High Patched: Yes CVE-2014-5389
CVE-2014-5389: Content Audit <= 1.6.0 - Authenticated (Admin+) SQL Injection

SQL injection vulnerability in content-audit-schedule.php in the Content Audit plugin before 1.6.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the "Audited content types" option in the content-audit page to wp-admin/options-general.php.

Published
Oct 01, 2014
Patched Release
1.6.1
Affected Versions
Versions before 1.6.1
Next Step
Update to 1.6.1 or newer if supported.
Review CVE-2014-5389 fixed version details Open CVE Reference