dbcve.org
BootplusApplication · Joeybling

CVE-2025-0698

HIGH · 8.8 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to after 2020-08-24 or later.
See remediation →
94/100
Remediation priority · Urgent
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 found in JoeyBling bootplus up to 247d5f6c209be1a5cf10cd0fa18e1d8cc63cf55d. It has been classified as critical. Affected is an unknown function of the file /admin/sys/menu/list. The manipulation of the argument sort/order leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

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

SQL injection vulnerability in JoeyBling bootplus at endpoint /admin/sys/menu/list via the sort/order parameter. An attacker can inject malicious SQL queries through unsanitized input. The vulnerability is remotely exploitable and a working exploit is publicly available.

MitigationImplement proper input validation and use parameterized queries (prepared statements) for all database operations in the affected menu list functionality. Restrict admin access to minimize attack surface until fix is deployed.

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
BootplusApplication
Affected:<= 2020-08-24

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the JoeyBling Bootplus version
    Locate the project metadata file (e.g., pom.xml, package.json, or build.gradle) and read the version declaration. Alternatively, check the build timestamp or commit date of the deployed application JAR/WAR file.
    Affected if The version is dated 2020-08-24 or earlier, or the version string indicates a build before that date.
  2. Verify the admin interface endpoint exists
    Check if the application exposes the /admin/sys/menu/list path by reviewing deployed web.xml configurations, application routing definitions, or by attempting a HEAD request to the endpoint (if authorized).
    Affected if The /admin/sys/menu/list endpoint is present and accessible in the running application.
  3. Confirm the sort and order parameters are accepted
    Review the controller or handler code for the /admin/sys/menu/list endpoint. Look for method signatures accepting 'sort' and 'order' request parameters, typically as query string parameters.
    Affected if The endpoint handler explicitly accepts and processes 'sort' and/or 'order' parameters.
  4. Inspect the database query implementation
    Locate the repository or service class that handles the menu list query. Examine the code that constructs the ORDER BY clause using the sort/order parameters. Look for string concatenation or string formatting used to build the SQL query.
    Affected if The sort/order parameter values are directly concatenated into the SQL ORDER BY clause without using parameterized queries, prepared statements, or input validation.

You are affected if you are running JoeyBling Bootplus version dated 2020-08-24 or earlier AND the /admin/sys/menu/list endpoint exists with unsanitized sort/order parameters used in dynamic SQL construction.

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
Upgrade available Upgrade to a release after 2020-08-24
Interim mitigation

Implement proper input validation and use parameterized queries (prepared statements) for all database operations in the affected menu list functionality. Restrict admin access to minimize attack surface until fix is deployed.

Fix this in Bootplus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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