CVE-2025-8529
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 was found in cloudfavorites favorites-web up to 1.3.0. Affected by this vulnerability is the function getCollectLogoUrl of the file app/src/main/java/com/favorites/web/CollectController.java. The manipulation of the argument url leads to server-side request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceServer-side request forgery (SSRF) in favorites-web up to v1.3.0. The getCollectLogoUrl function in CollectController.java accepts a user-controlled 'url' parameter without proper validation, allowing an attacker to make the server perform requests to arbitrary internal or external resources.
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 if favorites-web is deployedSearch for favorites-web application files, WAR archives, or running services in your environment. Check application directories, servlet containers, or container orchestration manifests.Affected if favorites-web is present in the environment
-
Check the installed version of favorites-webLocate the version metadata (pom.xml, package.json, MANIFEST.MF, or build artifacts) for the deployed favorites-web instance and compare it to v1.3.0.Affected if version is 1.3.0 or lower (any version up to and including v1.3.0)
-
Verify if CollectController is accessibleCheck if the CollectController.java class is compiled and loaded in the application. Look for endpoints related to 'collect' or 'logo' functionality in the application's routing configuration.Affected if CollectController is loaded and its endpoints are accessible via HTTP/HTTPS
-
Confirm the getCollectLogoUrl function is exposedReview application routing/endpoint mappings to determine if the getCollectLogoUrl function is exposed as a web endpoint that accepts a 'url' parameter.Affected if a web endpoint exists that accepts a 'url' parameter and passes it to getCollectLogoUrl
-
Check network isolation of the application serverInspect firewall rules, network policies, or application configuration to determine if the server can make outbound HTTP requests to arbitrary internal or external resources.Affected if the application server has unrestricted outbound network access and the vulnerable endpoint is exposed
The environment is affected if favorites-web version 1.3.0 or lower is deployed with the CollectController and its getCollectLogoUrl function exposed and accessible, allowing user-supplied 'url' parameters to trigger server-side requests.
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 strict URL allowlist validation for the url parameter, restrict outgoing network connections from the application server, and consider disabling the functionality if logo fetching from arbitrary URLs is not required.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8529 — 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-8529 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