dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11473

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability was identified in jflyfox jfinal_cms up to 5.1.0. This impacts the function list of the file AdvicefeedbackController.java. Such manipulation of the argument orderBy leads to sql injection. The attack can be launched remotely. The project was informed of the problem early through an issue report but has not responded yet.

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

SQL injection vulnerability in jflyfox jfinal_cms up to version 5.1.0. The list function of AdvicefeedbackController.java does not properly sanitize the orderBy parameter, allowing an attacker to manipulate SQL queries through this input vector. The vulnerability is exploitable remotely.

MitigationImplement parameterized queries or proper input validation/sanitization for the orderBy parameter in the affected AdvicefeedbackController.java list function. Until an official patch is released, consider implementing WAF rules to filter malicious orderBy input.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm jfinal_cms is deployed
    Locate the jfinal_cms application directory or WAR file in your environment. Check for the presence of the AdvicefeedbackController.java file within the source code or decompiled JAR.
    Affected if The application is jfinal_cms and the AdvicefeedbackController.java file exists in the codebase.
  2. Identify the installed version
    Find the version identifier in your jfinal_cms deployment. This may be in a pom.xml, build.gradle, version file, or Maven/Gradle metadata. Common locations include the project root, a version.properties file, or the WAR archive manifest.
    Affected if The version is 5.1.0 or any earlier version (e.g., 5.0.x, 4.x.x).
  3. Verify the vulnerable code path exists
    Locate AdvicefeedbackController.java in the source code and inspect the list function. Look for code that accepts an 'orderBy' parameter from the request and concatenates it directly into a SQL query string without using parameterized queries or input validation.
    Affected if The list function contains code that uses the orderBy parameter in a SQL query via string concatenation or string formatting (e.g., 'SELECT ... ORDER BY ' + orderBy).
  4. Confirm the endpoint is accessible
    Identify the URL path mapped to the AdvicefeedbackController list function (typically /advicefeedback/list or similar). Verify the web application is running and this endpoint is accessible via HTTP/HTTPS.
    Affected if The application exposes an HTTP endpoint that triggers the vulnerable list function.
  5. Check database query execution context
    Review the DAO or service layer that executes the constructed SQL query. Confirm that no input sanitization, allowlist validation, or framework query builders with parameterized order clauses are used for the orderBy value.
    Affected if The orderBy parameter flows from the controller to the SQL execution without sanitization or parameterization.

You are affected if you are running jfinal_cms version 5.1.0 or earlier, the AdvicefeedbackController.java file exists in your deployment, and the list function handles an orderBy parameter via direct string concatenation in SQL queries without sanitization.

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

Implement parameterized queries or proper input validation/sanitization for the orderBy parameter in the affected AdvicefeedbackController.java list function. Until an official patch is released, consider implementing WAF rules to filter malicious orderBy input.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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