The analysis of the vulnerability started with the information from the Wiz research blog post, which clearly described the vulnerability as a symbolic link bypass of a previous path traversal fix (CVE-2024-55947) in the PutContents API. The blog post detailed the attack chain, which involves creating a symbolic link in a repository and then using the PutContents API to write to it, causing an arbitrary file write. Based on this, I identified PutContents as the main vulnerable function. I then located the source code for this function in the gogs/gogs repository at internal/route/api/v1/repo/contents.go. The code confirms that the path is taken from the user-provided URL (c.Params("*")), and although it is cleaned using pathutil.Clean, there is no check to prevent the path from being a symbolic link. The cleaned path is then used in the UpdateRepoFile function, which performs the file write operation. This confirms that gogs.io/gogs/internal/route/api/v1/repo.PutContents is the vulnerable function that would be seen in a runtime profile during exploitation.