dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-14438

MEDIUM · 6.4 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Xagio SEO – AI Powered SEO plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.1.0.30 via the 'pixabayDownloadImage' function. This makes it possible for authenticated attackers, with Subscriber-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.

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 Xagio SEO WordPress plugin has a Server-Side Request Forgery (SSRF) vulnerability in the pixabayDownloadImage function, allowing authenticated users with Subscriber-level permissions to make arbitrary web requests from the server. This can be exploited to probe internal services, bypass firewalls, or exfiltrate data.

MitigationUpdate the plugin to a version beyond 7.1.0.30 when available; otherwise, disable the plugin or restrict user permissions to prevent Subscriber-level access until a patch is released.

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

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

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

  1. Confirm Xagio SEO plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Xagio SEO' in the list of active plugins
    Affected if Xagio SEO plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In the Plugins list, click on 'Xagio SEO' to view the plugin details, or check the plugin header file (usually in wp-content/plugins/xagio-seo/xagio.php) for the Version comment
    Affected if The version listed is 7.1.0.30 or earlier, or no version number is displayed indicating an outdated installation
  3. Check for subscriber-level user accounts
    Navigate to WordPress Users > All Users and review the Role column; look for any users assigned the 'Subscriber' role
    Affected if At least one user account with Subscriber role exists in the WordPress installation
  4. Verify the pixabayDownloadImage function is accessible
    Attempt to access the Pixabay image download feature via the plugin interface while logged in as a Subscriber user, or inspect the plugin file (xagio.php or related files) for the pixabayDownloadImage function definition and its capability checks
    Affected if The function exists in the plugin code and can be invoked by a user with Subscriber-level permissions without additional capability verification

You are affected if the Xagio SEO plugin is installed with version 7.1.0.30 or earlier AND at least one Subscriber-level user account exists in WordPress, allowing that user to trigger the vulnerable pixabayDownloadImage function.

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

Update the plugin to a version beyond 7.1.0.30 when available; otherwise, disable the plugin or restrict user permissions to prevent Subscriber-level access until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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