CVE-2025-0705
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 has been found in JoeyBling bootplus up to 247d5f6c209be1a5cf10cd0fa18e1d8cc63cf55d and classified as problematic. Affected by this vulnerability is the function qrCode of the file src/main/java/io/github/controller/QrCodeController.java. The manipulation of the argument text leads to open redirect. The attack can be launched 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 confidenceOpen redirect vulnerability in the qrCode function of QrCodeController.java in JoeyBling bootplus. The function accepts a user-controlled 'text' argument that is used in a redirect operation without proper validation, allowing attackers to craft malicious URLs that redirect victims to arbitrary sites.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm application is JoeyBling BootplusInspect your project dependencies (pom.xml, build.gradle, or compiled libraries) to verify the framework name matches JoeyBling Bootplus or JoeyBling bootplusAffected if The application does not use JoeyBling Bootplus framework - if different, this CVE does not apply
-
Determine installed versionCheck your project build file or library manifest for the bootplus version tag or date stamp; compare it against the affected range (all versions up to and including 2020-08-24)Affected if The version is 2020-08-24 or earlier, indicating a potentially vulnerable release
-
Locate QrCodeController.javaSearch your source code or decompiled application binaries for the file QrCodeController.java or the class QrCodeControllerAffected if This file does not exist in your deployment - the vulnerable code is not present
-
Verify qrCode endpoint exists and is exposedReview the QrCodeController for method mappings (such as @RequestMapping, @GetMapping) that expose a qrCode or similar function as a web-accessible endpointAffected if The qrCode function is not exposed as a web endpoint - the vulnerability requires user-supplied 'text' parameter input via HTTP request
-
Inspect redirect logic for the text parameterExamine the qrCode function code to verify whether the 'text' parameter is used directly in a redirect (such as 'redirect:') without validation against an allowlist or checks for relative paths and prohibited protocols (http:, https:, //)Affected if The code performs redirects using the 'text' parameter without validating it is a relative path or checking against an allowlist - this confirms the open redirect vulnerability is present
You are affected if you are running JoeyBling Bootplus version 2020-08-24 or earlier, have the QrCodeController with an exposed qrCode endpoint, and the 'text' parameter is used in redirect operations without validation.
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.
dbcve · scopedImplement strict URL validation for the redirect parameter - use an allowlist of permitted domains/paths, or validate that the redirect target is relative and does not contain external protocols (http:, https:, //) before performing any redirect.
Latest main branch commit (rolling release - any commit after 247d5f6c209be1a5cf10cd0fa18e1d8cc63cf55d)
- 1. Navigate to the bootplus project repository on GitHub
- 2. Check the commit history for src/main/java/io/github/controller/QrCodeController.java
- 3. Identify commits made after 247d5f6c209be1a5cf10cd0fa18e1d8cc63cf55d that address the open redirect in the qrCode function
- 4. Pull or checkout the latest code from the main branch which should contain the fix
- 5. If available, review the specific commit that patched the vulnerability to confirm the fix addresses CWE-601
- 6. Rebuild and redeploy the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0705 — 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-0705 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