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

CVE-2026-12095

HIGH · 7.2 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 Kargo Takip plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.2 via the 'api_url' parameter. 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. The script echoes internal API response data (specifically the value of any 'auth' key in a JSON response body) verbatim back to the attacker's browser, enabling direct exfiltration of responses from internal services such as cloud instance metadata endpoints.

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 Kargo Takip WordPress plugin (versions up to 1.2) contains an unauthenticated Server-Side Request Forgery vulnerability via the 'api_url' parameter, allowing remote attackers to make arbitrary web requests from the server and directly exfiltrate internal service responses including 'auth' key data from JSON API responses.

MitigationUpdate to a patched version of the plugin as soon as available; if no patch exists, disable the plugin immediately to prevent exploitation of the SSRF and potential internal metadata exposure.

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

CVSS:3.1/AV:N/AC:L/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. Verify Kargo Takip plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for 'kargo-takip' folder
    Affected if Plugin folder exists in the WordPress installation
  2. Check installed plugin version
    View plugin details in WordPress admin (Plugins > Installed Plugins > Kargo Takip) or read version from plugin's main PHP file header in /wp-content/plugins/kargo-takip/
    Affected if Version is 1.2 or lower (any version up to and including 1.2 is affected)
  3. Identify if plugin exposes API functionality
    Check if the plugin registers REST API routes or admin pages. Look for AJAX handlers or form submissions that accept an 'api_url' parameter by inspecting plugin source code or monitoring network requests to the site
    Affected if Plugin has endpoints that accept 'api_url' parameter without authentication
  4. Check for evidence of exploitation
    Review server access logs for requests to the plugin's endpoint with suspicious 'api_url' values, especially those targeting internal services or containing patterns like 'auth' in the response
    Affected if Logs show outbound requests from the server to unexpected internal/external destinations via the plugin, or sensitive 'auth' key data appears in server logs

A WordPress site is affected if the Kargo Takip plugin is installed with version 1.2 or lower and the plugin's API functionality with the 'api_url' parameter is accessible and enabled.

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 to a patched version of the plugin as soon as available; if no patch exists, disable the plugin immediately to prevent exploitation of the SSRF and potential internal metadata exposure.

Recommended fix Moderate confidence

Latest version available on wordpress.org (verify version > 1.2 or the version marked as patched)

  1. Check the current installed version of the Kargo Takip plugin in WordPress admin under Plugins > Installed Plugins
  2. Navigate to plugins.trac.wordpress.org or wordpress.org/plugins/kargo-takip to identify the latest stable release version
  3. Upgrade the plugin to the latest available version via WordPress admin: Plugins > Add New > Upload (or update if automatic updates are enabled)
  4. If no patched version is available from the official repository, consider temporarily disabling the Kargo Takip plugin until a fix is released
  5. If the plugin must remain active, restrict access to the affected endpoint via web server configuration (e.g., .htaccess rules) to block unauthenticated requests to the 'api_url' parameter
Caveat Review plugin changelog for any settings or API integration changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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