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

CVE-2025-10137

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Snow Monkey theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 29.1.5 via the request() function. This makes it possible for unauthenticated attackers 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 · moderate confidence

The Snow Monkey WordPress theme prior to version 29.1.5 contains a Server-Side Request Forgery (SSRF) vulnerability in its request() function. Unauthenticated attackers can exploit this to make arbitrary web requests from the server, potentially reaching internal services, querying sensitive information, or interacting with cloud metadata endpoints.

MitigationUpdate the Snow Monkey theme to version 29.1.6 or later. If immediate updates are not feasible, implement network segmentation and restrict outbound server traffic to prevent the server from making arbitrary requests to internal infrastructure.

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

CVSS:3.1/AV:N/AC:H/PR:N/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 Snow Monkey theme is installed
    Check the wp-content/themes/ directory for a folder named 'snow-monkey' or look for the theme in WordPress admin under Appearance > Themes
    Affected if The Snow Monkey theme files exist on the server
  2. Identify the installed Snow Monkey version
    Open wp-content/themes/snow-monkey/style.css and locate the 'Version:' field in the theme header comment
    Affected if The version number returned is less than 29.1.5 (the vulnerable version range is anything before 29.1.5)
  3. Verify the request() function exists and is accessible
    Search the theme files for the request() function definition - typically in includes/controller/canonical.php or similar includes files within the theme
    Affected if The request() function is present in the theme code and is callable without authentication
  4. Check if outbound HTTP requests are possible from the server
    Review the theme's configuration and any available network logging to determine if the server can make outbound HTTP requests
    Affected if The server has outbound network access and the vulnerable request() function can be invoked by unauthenticated users

You are affected if the Snow Monkey theme version is installed and is less than 29.1.5, and the request() function is present and accessible without authentication.

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 Snow Monkey theme to version 29.1.6 or later. If immediate updates are not feasible, implement network segmentation and restrict outbound server traffic to prevent the server from making arbitrary requests to internal infrastructure.

Recommended fix Moderate confidence

Version 29.1.6 or later (check WordPress theme repository for latest stable release)

  1. Update the Snow Monkey WordPress theme to the latest available version from the WordPress theme repository or the theme developer's official source
  2. After updating, verify the theme version reflects a release newer than 29.1.5
  3. Test critical site functionality to ensure the theme update does not break existing features
  4. Review any security-related release notes for the new version
Caveat Minor theme updates typically don't introduce breaking changes, but test in staging if your site has heavy customizations

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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