CVE-2025-7450
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 letseeqiji gorobbs up to 1.0.8. It has been classified as critical. This affects the function ResetUserAvatar of the file controller/api/v1/user.go of the component API. The manipulation of the argument filename leads to path traversal. It is possible to initiate the attack 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 confidenceA path traversal vulnerability exists in the ResetUserAvatar API function in controller/api/v1/user.go of the gorobbs application. The filename parameter is not properly validated, allowing attackers to use '../' sequences to traverse directories and potentially read or overwrite arbitrary files on the server.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm gorobbs application is runningIdentify processes or web services running gorobbs by checking running web applications, container processes, or service configurations that reference 'gorobbs'Affected if The gorobbs application is present in the environment
-
Locate the vulnerable source fileSearch for the file controller/api/v1/user.go in the gorobbs installation directory and examine the ResetUserAvatar function for unvalidated filename parameter handlingAffected if The file controller/api/v1/user.go exists and contains ResetUserAvatar function without proper input validation on the filename parameter
-
Check API endpoint exposureIdentify if the ResetUserAvatar API endpoint is accessible by reviewing API routing configuration files or attempting to access the endpoint (e.g., POST /api/v1/user/avatar/reset)Affected if The ResetUserAvatar API endpoint is exposed and accessible without additional authentication or rate limiting
-
Verify path traversal is possibleTest the filename parameter with traversal sequences like '../' in a non-production test environment to confirm the vulnerability existsAffected if The application accepts '../' sequences in the filename parameter and uses it in file operations without sanitization
A user is affected if gorobbs is running with the vulnerable ResetUserAvatar function in controller/api/v1/user.go that accepts unsanitized filename parameters containing '../' sequences.
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 input validation on the filename parameter using allowlist validation or canonicalize the path and verify it resolves within the expected directory. Consider using secure file handling methods that prevent directory traversal.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7450 — 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-7450 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