CVE-2025-7552
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 was found in Dromara Northstar up to 7.3.5. It has been rated as critical. Affected by this issue is the function preHandle of the file northstar-main/src/main/java/org/dromara/northstar/web/interceptor/AuthorizationInterceptor.java of the component Path Handler. The manipulation of the argument Request leads to improper access controls. The attack may be launched remotely. Upgrading to version 7.3.6 is able to address this issue. The patch is identified as 8d521bbf531de59b09b8629a9cbf667870ad2541. It is recommended to upgrade the affected component.
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 confidenceDromara Northstar up to 7.3.5 contains an improper access control vulnerability in the AuthorizationInterceptor's preHandle method. The issue allows manipulation of the Request argument to bypass authorization checks, potentially enabling unauthorized access to protected endpoints.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Dromara Northstar installationLocate the Northstar application or library in your environment. Check build files (pom.xml, build.gradle), dependency manifests, or application JAR/WAR files for the presence of Dromara Northstar components.Affected if Dromara Northstar component is present in your environment
-
Determine installed Northstar versionCheck the version of the Dromara Northstar library or application. Inspect pom.xml, build.gradle, MANIFEST.MF inside JAR files, or the application's version metadata. Compare the version number to the affected range: versions 7.3.5 and below are vulnerable; version 7.3.6 and later are fixed.Affected if The installed version is 7.3.5 or earlier
-
Verify AuthorizationInterceptor is in useInspect the application configuration or source code for the AuthorizationInterceptor class, specifically its preHandle method. Check Spring MVC configuration files, XML context files, or annotation-based configurations that define interceptors.Affected if AuthorizationInterceptor with preHandle method is configured and handles incoming requests
-
Confirm protected endpoints existReview the application's endpoint definitions (controllers, mappings) to identify which routes require authorization. Check for @Secured, @PreAuthorize annotations or security configuration that relies on the AuthorizationInterceptor.Affected if There are endpoints protected by the vulnerable AuthorizationInterceptor
-
Check for request manipulation exposureAnalyze application logs, access logs, or security monitoring for unusual request patterns that modify the Request object before authorization evaluation. This may require reviewing custom code that processes HttpServletRequest before the interceptor runs.Affected if Custom request processing code exists that could manipulate the Request argument before authorization checks
Your environment is affected if Dromara Northstar version 7.3.5 or earlier is installed and the AuthorizationInterceptor is configured to protect endpoints, since the vulnerability allows bypassing these authorization checks through Request argument manipulation.
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 · scopedUpgrade the Dromara Northstar component to version 7.3.6 or later to apply the patch (commit 8d521bbf531de59b09b8629a9cbf667870ad2541) that addresses this authorization bypass.
7.3.6
- Identify all deployments running Dromara Northstar version 7.3.5 or earlier
- Plan and schedule a maintenance window for the upgrade
- Back up current configuration and any persistent data
- Upgrade the Northstar component to version 7.3.6
- Verify the upgrade was successful by checking the version number and ensuring the application functions correctly
- Test the specific functionality that was vulnerable (the AuthorizationInterceptor preHandle method) to confirm the improper access control issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7552 — 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-7552 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