CVE-2026-5147
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 · uneditedA security flaw has been discovered in YunaiV yudao-cloud up to 2026.01. This affects an unknown part of the file /admin-api/system/tenant/get-by-website. The manipulation of the argument Website results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceSQL injection vulnerability in the /admin-api/system/tenant/get-by-website endpoint of yudao-cloud. The 'Website' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through this unauthenticated or authenticated API endpoint.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify yudao-cloud installationLocate the yudao-cloud application directory or check running services for yudao-cloud (common paths include /opt/yudao-cloud, /var/www/yudao-cloud, or check process list for yudao-related Java processes)Affected if yudao-cloud is present in the environment
-
Determine yudao-cloud versionCheck the application version file (such as pom.xml, package.json, or a version.properties file in the yudao installation directory) or query the application's info endpoint if availableAffected if The installed version does not have the CVE-2026-5147 patch applied (compare against any vendor release notes or security advisories)
-
Verify admin API endpoint exposureAttempt to access or probe the /admin-api/system/tenant/get-by-website endpoint (e.g., curl -X GET http://localhost:port/admin-api/system/tenant/get-by-website or check if the route is registered in the application's routing configuration)Affected if The endpoint is accessible without proper access controls or the route exists in the application
-
Check authentication configurationReview the application's security configuration for the /admin-api/* endpoints to determine if get-by-website requires authentication, or test the endpoint with and without valid credentialsAffected if The endpoint can be reached without authentication or with weak authentication controls
A system is affected if it runs a vulnerable version of yudao-cloud with the /admin-api/system/tenant/get-by-website endpoint exposed and accessible, allowing SQL injection through the Website parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for the Website parameter; deploy a WAF rule to block SQL injection patterns as an interim measure; restrict access to this admin API endpoint until a patch is available from the vendor.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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