dbcve.org
WeknoraApplication · Tencent

CVE-2025-11046

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Public exploit 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
A security flaw has been discovered in Tencent WeKnora 0.1.0. This impacts the function testEmbeddingModel of the file /api/v1/initialization/embedding/test. The manipulation of the argument baseUrl results in server-side request forgery. The attack can be launched remotely. The exploit has been released to the public and may be exploited. It is advisable to upgrade the affected component. The vendor responds: "We have confirmed that the issue mentioned in the report does not exist in the latest releases".

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

Server-Side Request Forgery (SSRF) vulnerability in Tencent WeKnora 0.1.0 allows remote attackers to manipulate the baseUrl parameter in the /api/v1/initialization/embedding/test endpoint (testEmbeddingModel function) to make the server perform arbitrary requests to attacker-controlled resources.

MitigationUpgrade to the latest version of Tencent WeKnora; if upgrade is not possible, implement strict allowlist validation for the baseUrl parameter to only permit trusted endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WeknoraApplication
Affected:= 0.1.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Tencent WeKnora installation
    Locate the WeKnora application installation directory or check running services for WeKnora. Common locations include /opt/weknora, /usr/local/weknora, or check running processes for 'weknora' or 'wek'
    Affected if Tencent WeKnora version 0.1.0 is installed and running
  2. Verify the installed version
    Check the version of Tencent WeKnora by inspecting the application metadata, package.json, setup.py, or the main application file where version is defined. Run: find . -name 'package.json' -o -name 'setup.py' -o -name 'version*' 2>/dev/null | xargs grep -i version 2>/dev/null
    Affected if The version returned is exactly 0.1.0
  3. Confirm the vulnerable endpoint exists
    Check if the file containing the testEmbeddingModel function exists. Look for routes or API definitions that map to /api/v1/initialization/embedding/test. Inspect the application source code for the testEmbeddingModel function definition
    Affected if The endpoint /api/v1/initialization/embedding/test is defined and the testEmbeddingModel function exists in the codebase
  4. Check if the endpoint is accessible without authentication
    Attempt to access the endpoint with a GET or POST request, providing a test baseUrl value such as http://localhost:9999. Example: curl -X POST http://<server>/api/v1/initialization/embedding/test -d '{"baseUrl":"http://example.com"}'
    Affected if The endpoint responds without requiring authentication or proper authorization, allowing arbitrary baseUrl parameter values

You are affected if Tencent WeKnora version 0.1.0 is installed and the /api/v1/initialization/embedding/test endpoint with the baseUrl parameter is accessible without strict validation.

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

Upgrade to the latest version of Tencent WeKnora; if upgrade is not possible, implement strict allowlist validation for the baseUrl parameter to only permit trusted endpoints.

Recommended fix Moderate confidence

latest stable release

  1. 1. Upgrade Tencent Weknora to the latest stable release available from the vendor
  2. 2. After upgrading, verify that the /api/v1/initialization/embedding/test endpoint no longer allows arbitrary baseUrl manipulation
  3. 3. Confirm the SSRF vulnerability is remediated by testing the endpoint with an internal IP address (e.g., 127.0.0.1) as baseUrl - the request should be rejected or fail

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

Fix this in Weknora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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