CVE-2025-0701
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 vulnerability classified as critical has been found in JoeyBling bootplus up to 247d5f6c209be1a5cf10cd0fa18e1d8cc63cf55d. This affects an unknown part of the file /admin/sys/user/list. The manipulation of the argument sort leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not 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 confidenceA critical SQL injection vulnerability exists in JoeyBling bootplus admin panel. The 'sort' parameter in the /admin/sys/user/list endpoint is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code. The exploit is publicly available.
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<= 2020-08-24CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify JoeyBling Bootplus installationLocate the Bootplus application files or check the application's version information as displayed in the admin panel interfaceAffected if Bootplus admin panel is present and the version displays as 2020-08-24 or earlier
-
Verify the vulnerable endpoint existsCheck if the application serves the /admin/sys/user/list endpoint by reviewing the web server configuration or attempting to access the URL (if authorized)Affected if The endpoint /admin/sys/user/list is present and accessible within the application
-
Confirm admin panel is exposedReview network configuration and access controls to determine if the /admin/* routes are reachable from network locations beyond trusted admin workstationsAffected if The admin panel is accessible from network segments outside the trusted administrative zone
-
Check for indicators of compromiseReview web server access logs and application logs for requests to /admin/sys/user/list containing SQL operators (UNION, SELECT, INSERT, DROP, --, ;, ') in the sort parameterAffected if Log analysis reveals suspicious SQL injection patterns in the sort parameter against the user list endpoint
-
Audit user accounts for unauthorized changesQuery the underlying database or application user management to check for unexpected administrative accounts or modifications to existing user recordsAffected if Unexpected administrative accounts exist or user records show unauthorized modifications
A user is affected if JoeyBling Bootplus version 2020-08-24 or earlier is installed, the admin panel is accessible, and the /admin/sys/user/list endpoint is present with the vulnerable sort 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 dataApply input validation and parameterized queries to the sort parameter immediately. Monitor for indicators of compromise given public exploit availability. Once the vendor releases an updated rolling-release version, deploy it promptly.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-0701 — 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-2025-0701 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