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

CVE-2025-49374

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-22
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 captcha.eu Captcha.eu captcha-eu allows Server Side Request Forgery.This issue affects Captcha.eu: from n/a through <= 1.0.61.

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 captcha.eu WordPress plugin allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources. The vulnerability exists in captcha-eu plugin versions through 1.0.61, likely due to insufficient validation of user-supplied URL parameters used in server-side request operations.

MitigationUpgrade captcha.eu captcha-eu plugin to version 1.0.62 or later. If upgrade is not immediately possible, implement URL allowlisting at the web application firewall (WAF) level to restrict outgoing requests to trusted domains 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
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. Locate the captcha-eu plugin version
    Access your WordPress admin panel, go to Plugins > Installed Plugins, and find the captcha.eu (captcha-eu) plugin to read the installed version number
    Affected if The version listed is 1.0.61 or lower
  2. Check plugin files for version string
    If admin access is unavailable, inspect the plugin directory (wp-content/plugins/captcha-eu/) and open the main plugin file or readme.txt to find the version metadata
    Affected if The version string shows 1.0.61 or any version below 1.0.62
  3. Verify the plugin is active
    In WordPress admin under Plugins, confirm the captcha-eu plugin status shows as Active
    Affected if The plugin is installed and active with a vulnerable version (1.0.61 or lower)
  4. Check for exposed captcha forms
    Review your WordPress site for any pages displaying the captcha.eu captcha (login form, registration, comment form, contact forms, or custom forms) - these are the entry points that could trigger the SSRF via URL parameters
    Affected if Captcha forms are publicly accessible and the plugin version is 1.0.61 or lower

You are affected if the captcha-eu plugin is installed with version 1.0.61 or lower and is actively displaying captcha challenges on your site.

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

Upgrade captcha.eu captcha-eu plugin to version 1.0.62 or later. If upgrade is not immediately possible, implement URL allowlisting at the web application firewall (WAF) level to restrict outgoing requests to trusted domains only.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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