dbcve.org
AiomaticWordPress extension · Coderevolution

CVE-2025-6206

HIGH · 7.5 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 2.5.1 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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
The Aiomatic - Automatic AI Content Writer & Editor, GPT-3 & GPT-4, ChatGPT ChatBot & AI Toolkit plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'aiomatic_image_editor_ajax_submit' function in all versions up to, and including, 2.5.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. In order to exploit the vulnerability, there must be a value entered for the Stability.AI API key. The value can be arbitrary.

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

The Aiomatic plugin for WordPress contains an arbitrary file upload vulnerability in the aiomatic_image_editor_ajax_submit function. Authenticated attackers with Subscriber-level access can upload arbitrary files due to missing file type validation, potentially achieving remote code execution. The exploit requires a value (even arbitrary) in the Stability.AI API key field.

MitigationUpdate to a version beyond 2.5.0 once a patch is released, and if the Stability.AI API key field is not needed, remove or blank it to reduce the attack surface.

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
AiomaticWordPress extension
Affected:< 2.5.1

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 Aiomatic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Aiomatic' by Coderevolution, or check the file system at /wp-content/plugins/aiomatic/ for the presence of the plugin directory
    Affected if Aiomatic plugin is not installed on the WordPress site
  2. Determine installed plugin version
    Check the plugin header in /wp-content/plugins/aiomatic/aiomatic.php for the 'Version' field, or view the plugin details in WordPress admin Plugins page
    Affected if Version is less than 2.5.1 (e.g., 2.5.0, 2.4.x, etc.)
  3. Check Stability.AI API key configuration
    Navigate to WordPress admin > Aiomatic Settings > API Keys tab, or inspect the wp_options table for option_name containing 'stability_api_key' or similar, and verify if any value (even a placeholder or arbitrary string) is present in the Stability.AI API key field
    Affected if A value exists in the Stability.AI API key field (even arbitrary/placeholder text)
  4. Verify Subscriber-level user access exists
    In WordPress admin > Users, check if any users have the Subscriber role assigned, or query the wp_usermeta table for meta_value='subscriber'
    Affected if At least one Subscriber-level user account exists on the site

The environment is affected if Aiomatic plugin version is below 2.5.1 AND a value (any value) is present in the Stability.AI API key field, allowing authenticated Subscriber-level users to potentially exploit the arbitrary file upload vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2.5.1 or later
Fixed in 2.5.1
Interim mitigation

Update to a version beyond 2.5.0 once a patch is released, and if the Stability.AI API key field is not needed, remove or blank it to reduce the attack surface.

Recommended fix High confidence

2.5.1

  1. Upgrade the Aiomatic plugin to version 2.5.1 or later through the WordPress plugin repository or your site's plugin management interface
  2. Verify the upgrade was successful by checking the installed plugin version
  3. Confirm the 'aiomatic_image_editor_ajax_submit' function now properly validates file types before allowing uploads
  4. Review any recently uploaded files on the server for suspicious content as a precautionary measure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aiomatic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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