dbcve.org
Ai Content Writing AssistantWordPress extension · Rayhan1

CVE-2023-45063

HIGH · 8.8 CVSS v3.1 Published 2023-10-12
Fix available
A fix is available. Upgrade to after 1.1.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in ReCorp AI Content Writing Assistant (Content Writer, GPT 3 & 4, ChatGPT, Image Generator) All in One plugin <= 1.1.5 versions.

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 · high confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the ReCorp AI Content Writing Assistant WordPress plugin affecting versions 1.1.5 and below. The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations, allowing attackers to trick authenticated administrators into unknowingly performing actions such as modifying plugin settings or generating content. An attacker would need to lure a logged-in administrator to click a malicious link or visit a crafted webpage to trigger the forged request.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all POST/GET state-changing actions and verify the Origin/Referer headers. Alternatively, update to a patched version of the plugin if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ai Content Writing AssistantWordPress extension
Affected:<= 1.1.5

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate 'Rayhan1 Ai Content Writing Assistant' or 'ReCorp AI Content Writing Assistant'. Note the version number displayed. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/rayhan1-ai-content-writing-assistant/ or similar) for the 'Version' header in the plugin comment block.
    Affected if The plugin is installed and the version is 1.1.5 or lower
  2. Identify state-changing admin actions
    Examine the plugin's PHP files for functions that perform state-changing operations such as saving settings, updating options, generating content, or modifying database records. Look for functions hooked to admin_init, admin_post, or AJAX handlers that accept user input and modify system state.
    Affected if The plugin handles admin actions that modify settings, content, or database records without explicit mention of nonce verification in the code
  3. Inspect nonce validation in action handlers
    Open the PHP files containing the state-changing functions identified in step 2. Search for presence of wp_verify_nonce, check_admin_referer, wp_create_nonce, or check_ajax_referer calls within these functions. Specifically verify that each function that modifies data includes a nonce verification call before processing the request.
    Affected if State-changing admin functions lack wp_verify_nonce(), check_admin_referer(), or equivalent nonce validation calls, or if these calls are present but placed after the action logic rather than before
  4. Check nonce implementation in forms and URLs
    Review the plugin's admin pages and frontend forms for hidden nonce fields (typically created with wp_nonce_field) or nonce URLs (using wp_nonce_url). Verify that every form submission and AJAX request that triggers state changes includes a valid nonce value that corresponds to the verification found in step 3.
    Affected if Forms and AJAX requests performing state-changing operations do not include nonce fields, or the nonces present are not validated server-side in the corresponding handler functions

You are affected if the Rayhan1 Ai Content Writing Assistant plugin (version 1.1.5 or below) is installed and its state-changing admin actions lack proper nonce validation as demonstrated by missing or inadequate wp_verify_nonce calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.1.5
Interim mitigation

Implement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all POST/GET state-changing actions and verify the Origin/Referer headers. Alternatively, update to a patched version of the plugin if available.

Fix this in Ai Content Writing Assistant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45063 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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