dbcve.org
RebuildApplication · Getrebuild

CVE-2025-50900

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-25
Fix available
A fix is available. Upgrade to after 4.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
An issue was discovered in getrebuild/rebuild 4.0.4. The affected source code class is com.rebuild.web.RebuildWebInterceptor, and the affected function is preHandle In the filter code, use CodecUtils.urlDecode(request.getRequestURI()) to obtain the URL-decoded request path, and then determine whether the path endsWith /error. If so, execute return true to skip this Interceptor. Else, redirect to /user/login api. Allowing unauthenticated attackers to gain sensitive information or escalated privileges.

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

The RebuildWebInterceptor in getrebuild/rebuild v4.0.4 contains an authentication bypass vulnerability in its preHandle method. The interceptor attempts to skip authentication for paths ending with '/error' by using URL-decoded URI comparison with endsWith. Attackers can craft malicious URLs to bypass this check and access protected resources without authentication, potentially gaining sensitive information or escalated privileges.

MitigationFix the interceptor logic to properly enforce authentication checks for all protected paths rather than relying on a simple string ending check. Implement robust path validation and ensure all non-public endpoints require valid authentication.

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
RebuildApplication
Affected:<= 4.0.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Rebuild version
    Locate the build manifest, WAR file version, or application properties file that contains the Rebuild version number. Common locations include version.properties, MANIFEST.MF in the JAR/WAR, or the about page in the web UI.
    Affected if The version is 4.0.4 or any earlier version of Rebuild v4.x.
  2. Locate the RebuildWebInterceptor class
    Search the deployed application codebase or decompiled classes for the file RebuildWebInterceptor.java. This is typically found in the web module package structure. Verify the preHandle method contains logic that checks for '/error' path endings.
    Affected if The RebuildWebInterceptor class exists and contains a preHandle method that uses endsWith to skip authentication for paths ending with '/error'.
  3. Verify the URL path matching logic
    Examine the preHandle method code to confirm it performs URL-decoded URI comparison using endsWith for the '/error' path check. Look for the specific condition that allows the bypass.
    Affected if The code shows that the authentication skip relies solely on endsWith('/error') against the decoded URI without additional validation.
  4. Check if the application has protected endpoints
    Review the application's URL routing configuration or security configuration to identify which endpoints require authentication. Look for patterns that would typically be protected but could be reached via the vulnerable interceptor logic.
    Affected if Protected endpoints exist and the RebuildWebInterceptor is registered in the filter chain before authentication filters.
  5. Test for authentication bypass
    If you have access to a test environment, attempt to access a protected resource using a URL that might bypass the endsWith('/error') check, such as URL-encoded variations or path traversal patterns that resolve to protected paths.
    Affected if Requests to protected endpoints succeed without authentication when using crafted URLs that bypass the '/error' path check logic.

You are affected if the installed Rebuild version is 4.0.4 or earlier and the RebuildWebInterceptor with the vulnerable preHandle logic is active in the request filter chain.

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 4.0.4
Interim mitigation

Fix the interceptor logic to properly enforce authentication checks for all protected paths rather than relying on a simple string ending check. Implement robust path validation and ensure all non-public endpoints require valid authentication.

Fix this in Rebuild 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-50900 — 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-50900 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