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

CVE-2025-10874

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-24
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 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 Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More WordPress plugin before 3.0.2 does not limit URLs which may be used for the stock photo import feature, allowing the user to specify arbitrary URLs. This leads to a server-side request forgery as the user may force the server to access any URL of their choosing.

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 Orbit Fox WordPress plugin before version 3.0.2 contains a server-side request forgery (SSRF) vulnerability in its stock photo import feature. The plugin does not validate or restrict the URLs that users can specify for importing stock photos, allowing authenticated users to cause the server to make requests to arbitrary URLs controlled by the attacker.

MitigationUpdate the Orbit Fox plugin to version 3.0.2 or later, which should include proper URL validation. If immediate update is not possible, restrict the stock photo import feature to trusted users only.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify Orbit Fox plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Orbit Fox' in the list. Note the version number displayed under the plugin name.
    Affected if Orbit Fox plugin is present and the displayed version is lower than 3.0.2 (e.g., 3.0.1, 3.0.0, or any version before 3.0.2).
  2. Confirm plugin version via file inspection
    If the admin dashboard is not accessible, inspect the main plugin file (typically wp-content/plugins/orbitfox/main.php or similar) and locate the version comment or header definition.
    Affected if The version defined in the plugin header is below 3.0.2.
  3. Identify if stock photo import feature is active
    Check the WordPress admin menu for a Stock Photos or similar import option (often under the Orbit Fox plugin menu or Appearance > Stock Photos). Look for any active widgets or modules that include stock photo functionality.
    Affected if The stock photo import feature or module is present and enabled in the plugin settings.
  4. Audit user roles with access to stock photo import
    Review WordPress user roles and capabilities. Check if users with Subscriber, Contributor, Author, or Editor roles can access the stock photo import functionality. Inspect the capability required to use the feature if visible in the code.
    Affected if Users other than Administrators (such as Authors, Editors, or lower roles) can access or trigger the stock photo import feature.

The environment is affected if the Orbit Fox plugin version is below 3.0.2 AND the stock photo import feature is active with access granted to non-administrator users.

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

Update the Orbit Fox plugin to version 3.0.2 or later, which should include proper URL validation. If immediate update is not possible, restrict the stock photo import feature to trusted users only.

Recommended fix High confidence

Orbit Fox plugin version 3.0.2 or later

  1. Backup your WordPress database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Orbit Fox plugin in the list
  4. If an update is available, click 'Update Now' to upgrade to version 3.0.2 or later
  5. Alternatively, upload and install Orbit Fox version 3.0.2 or newer manually via Plugins > Add New > Upload Plugin
  6. Verify the updated version number in the plugin list after updating
  7. Test the stock photo import feature to confirm functionality works as expected after the update
Caveat Review the plugin changelog for any compatibility notes with your WordPress version or other installed plugins

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

Have this fixed 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 help mitigating

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-2025-10874 — 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-10874 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