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

CVE-2025-30964

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-15
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
Server-Side Request Forgery (SSRF) vulnerability in ThemeGoods Photography photography allows Server Side Request Forgery.This issue affects Photography: from n/a through < 7.7.6.

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

Server-Side Request Forgery (SSRF) vulnerability in the ThemeGoods Photography WordPress theme allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources. The vulnerability affects versions prior to 7.7.6 and can be exploited with low privileges via network access, potentially enabling reconnaissance, access to internal services, or cloud metadata endpoints.

MitigationUpdate the ThemeGoods Photography theme to version 7.7.6 or later to remediate the vulnerability. If immediate patching is not feasible, implement network segmentation to restrict outbound connections from the web server and monitor for requests to internal IP ranges (127.0.0.1, 10.x.x.x, 169.254.169.254) or suspicious external domains.

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. Identify if ThemeGoods Photography theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'photography' or similar ThemeGoods theme folder. In WordPress admin, go to Appearance > Themes to list installed themes.
    Affected if The ThemeGoods Photography theme is present in the WordPress installation.
  2. Determine the installed theme version
    Open the theme's style.css file in the photography theme folder and look for the 'Version:' header in the file comments. Alternatively, in WordPress admin, click on the theme details to view the version number.
    Affected if The version number found is below 7.7.6 (e.g., 7.7.5, 7.7.0, etc.).
  3. Verify the theme is active on the WordPress site
    In WordPress admin, go to Appearance > Themes and check if the Photography theme is currently activated. Alternatively, check the wp_options table for the 'template' or 'stylesheet' option value matching the theme folder name.
    Affected if The Photography theme is activated and serving pages on the site.
  4. Check for SSRF-prone functionality in theme code
    Search the theme's PHP files (particularly in includes/, functions.php, or any ajax-handling files) for functions that make HTTP requests (wp_remote_get, wp_remote_post, curl_exec, file_get_contents with URLs) without proper validation. Look for parameters that accept URLs or endpoints.
    Affected if URL-handling code exists without proper validation or allowlist controls, and the theme is vulnerable code is present.
  5. Review server logs for suspicious outbound requests
    Examine web server access logs (Apache access_log, Nginx access.log) and WordPress debug logs for unusual outbound requests. Look for requests to internal IPs (127.0.0.1, 10.x.x.x, 172.16.x.x, 192.168.x.x) or cloud metadata endpoints (169.254.169.254) originating from the server.

You are affected if the ThemeGoods Photography theme is installed, activated, and running version 7.7.5 or lower, as the vulnerable SSRF code exists in those versions and can be exploited by any authenticated user with low privileges.

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 ThemeGoods Photography theme to version 7.7.6 or later to remediate the vulnerability. If immediate patching is not feasible, implement network segmentation to restrict outbound connections from the web server and monitor for requests to internal IP ranges (127.0.0.1, 10.x.x.x, 169.254.169.254) or suspicious external domains.

Recommended fix Moderate confidence

7.7.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Photography theme by ThemeGoods
  4. 4. Check the current version to confirm it is below 7.7.6
  5. 5. If an update is available, click Update Now to upgrade to version 7.7.6 or later
  6. 6. Alternatively, download the latest version of the Photography theme from a trusted source (such as the official ThemeGoods marketplace or ThemeForest)
  7. 7. Upload and install the updated theme through WordPress admin or via FTP
  8. 8. After updating, verify the new version number is 7.7.6 or higher

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-30964 — 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-30964 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