CVE-2025-8084
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 · uneditedThe AI Engine plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.8 via the rest_helpers_create_images function. This makes it possible for authenticated attackers, with Editor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. On Cloud instances, this issue allows for metadata retrieving.
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 confidenceThe AI Engine WordPress plugin contains an SSRF vulnerability in the rest_helpers_create_images function that allows authenticated users with Editor-level access or higher to make arbitrary web requests from the server, potentially accessing internal services and sensitive metadata on cloud platforms.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify AI Engine plugin is installedNavigate to WordPress admin dashboard > Plugins and confirm the AI Engine plugin is active and installedAffected if AI Engine plugin is installed and active
-
Determine installed plugin versionIn WordPress admin > Plugins > AI Engine, view the plugin version details. Compare against the affected range (versions 3.1.8 and below)Affected if Installed version is 3.1.8 or lower
-
Confirm user role accessReview WordPress user roles to determine if any accounts hold Editor-level or higher privileges (Editor, Author, Contributor, Administrator)Affected if Any user accounts with Editor or higher access exist in the system
-
Identify vulnerable endpoint exposureCheck if the REST API endpoint /wp-json/ai-engine/v1/create_images is publicly accessible or accessible to authenticated non-admin users. This can be tested by sending a request to that endpoint with valid authentication from an Editor-level accountAffected if The rest_helpers_create_images endpoint responds to requests from users with Editor-level access
You are affected if the AI Engine plugin version is 3.1.8 or lower AND your site has users with Editor-level or higher access who can reach the vulnerable REST API endpoint.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the AI Engine plugin to a version beyond 3.1.8. Additionally, restrict access to the vulnerable endpoint to only trusted administrators and implement network segmentation to prevent the web server from reaching internal infrastructure.
Version 3.1.9 or later
- Update the AI Engine plugin for WordPress to the latest available version from the official WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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