← WordPress Vulnerabilities
WordPress security by component

GPT3 AI Content Writer

GPT3 AI Content Writer is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 07, 2025; the highest CVE/CNA score is 6.5.

Plugin slug: gpt3-ai-content-generator

CVE-2025-47470: GPT3 AI Content Writer: Cross-site request forgery

GPT3 AI Content Writer is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

PublishedMay 07, 2025
Safe version guidanceSee mitigation notes
Safe version
May 07, 2025 CVE-2025-47470
GPT3 AI Content Writer: Cross-site request forgery
GPT3 AI Content Writer is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVDPending
Jul 21, 2024 CVE-2024-37465
GPT3 AI Content Writer: Cross-site scripting
GPT3 AI Content Writer is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.5
NVD5.4
Feb 29, 2024 CVE-2023-51528
AI Power: Complete AI Pack – Powered by GPT-4: Cross-site request forgery
AI Power: Complete AI Pack – Powered by GPT-4 is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVD8.8
Dec 29, 2023 CVE-2023-51527
AI Power: Complete AI Pack – Powered by GPT-4: A security weakness
AI Power: Complete AI Pack – Powered by GPT-4 is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVD7.5