dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-32247

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 ABCdatos AI Content Creator ai-content-creator allows Cross Site Request Forgery.This issue affects AI Content Creator: from n/a through <= 1.2.6.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the ABCdatos AI Content Creator WordPress plugin allows attackers to induce authenticated users to perform unintended actions. The vulnerability affects versions up to and including 1.2.6, enabling malicious requests to be forged on behalf of logged-in administrators.

MitigationImplement anti-CSRF tokens on all state-changing operations (forms and AJAX actions), add SameSite attribute to session cookies, and validate the Origin or Referer header on POST requests to prevent cross-site request forgery attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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
    In WordPress admin, go to Plugins > Installed Plugins and locate 'ABCdatos AI Content Creator'. Check the version number displayed under the plugin name. Alternatively, inspect the plugin's main PHP file header for the Version tag.
    Affected if The plugin is installed and the version is 1.2.6 or lower.
  2. Identify state-changing admin forms
    Navigate to the plugin's admin pages (typically under 'AI Content Creator' in the left sidebar). Inspect HTML forms that perform actions like saving settings, creating content, or modifying configuration. View the page source to examine form markup.
    Affected if Forms exist that perform actions without a hidden CSRF token field (look for input fields named 'nonce', '_wpnonce', or similar).
  3. Check AJAX action endpoints for nonce validation
    In the plugin directory, locate PHP files handling AJAX requests (typically using 'wp_ajax_' hooks). Search for the presence of 'wp_verify_nonce' or 'check_ajax_referer' function calls within these handlers.
    Affected if AJAX handlers exist that process requests without calling nonce verification functions.
  4. Examine cookie configuration for SameSite attribute
    Using browser developer tools (Application tab > Cookies) or by inspecting PHP session configuration, check if session cookies set by the plugin include the SameSite attribute.
    Affected if Session cookies lack the SameSite attribute or have it set to 'None' without the Secure flag.

A user is affected if the ABCdatos AI Content Creator plugin version 1.2.6 or lower is installed and any state-changing operations (admin forms or AJAX actions) lack CSRF token protection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations (forms and AJAX actions), add SameSite attribute to session cookies, and validate the Origin or Referer header on POST requests to prevent cross-site request forgery attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32247 — 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-2025-32247 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