CVE-2025-30037
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 · uneditedThe system exposes several endpoints, typically including "/int/" in their path, that should be restricted to internal services, but are instead publicly accessible without authentication to any host able to reach the application server on port 443/tcp.
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 · moderate confidenceInternal API endpoints containing '/int/' in their URL path are exposed to the public internet without authentication. Any host that can reach the application's HTTPS port (443/tcp) can access these endpoints that should be restricted to internal services only, potentially exposing sensitive functionality or data.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 if the application has /int/ path endpointsReview application routing configuration, API documentation, or perform web crawling to discover endpoints containing '/int/' in their URL paths. Check routes.js, api.yaml, or similar routing definitions.Affected if The application exposes any endpoints with '/int/' in the URL path that should be restricted to internal services.
-
Test unauthenticated access to /int/ endpoints from external networkSend HTTP/HTTPS requests to discovered /int/ endpoints without providing any authentication credentials. Use a tool like curl or a network scanner from outside the internal network.Affected if The /int/ endpoints respond with valid data or acceptable HTTP responses (not 401/403) when accessed without authentication.
-
Verify network-level access controls for /int/ pathsReview firewall rules, VPC security groups, WAF configurations, or reverse proxy settings to determine if access to /int/ paths is restricted to specific internal IP ranges or authorized networks.Affected if No network-level restrictions exist that limit /int/ endpoint access to internal IP addresses only.
-
Check application-layer authentication for internal endpointsExamine the application's authentication and authorization middleware, route guards, or API security configuration to verify that /int/ paths require valid authentication or are explicitly blocked for external requests.Affected if The application does not enforce authentication, authorization, or IP-based restrictions for /int/ endpoint access.
The environment is affected if the application exposes /int/ endpoints that are accessible from external networks without requiring authentication or network-level access controls.
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 dataImplement network-level access controls (firewall rules, VPC security groups, or WAF rules) to restrict access to /int/ paths to authorized internal IP ranges, or add proper authentication/authorization checks at the application layer for these endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30037 — 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-30037 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