[Snyk] Security upgrade axios from 1.4.0 to 1.7.4

[naiba4]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-7361793	833

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

⚠️ No Changeset found

Latest commit: 84b5ef2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/axios@1.7.4	network Transitive: environment, filesystem	+8	2.49 MB	jasonsaayman
npm/vue@3.3.4	environment, eval Transitive: filesystem, unsafe	+19	13.5 MB	yyx990803

🚮 Removed packages: npm/@sentry/browser@7.36.0, npm/axios@1.4.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Uses eval	npm/vue@3.3.4	Eval Type: Function Location: Package overview	package-lock.json theme/package.json	🚫
Environment variable access	npm/vue@3.3.4	Env Vars: NODE_ENV Location: Package overview	package-lock.json theme/package.json	🚫
Environment variable access	npm/ws@8.12.0	Env Vars: WS_NO_BUFFER_UTIL Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/ws@8.12.0	Env Vars: WS_NO_UTF_8_VALIDATE Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/vue-eslint-parser@9.1.0	Location: Package overview	package-lock.json package.json	🚫
Debug access	npm/vue-eslint-parser@9.1.0	Module: module Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/vue-eslint-parser@9.1.0	Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: DEBUG Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: CI Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: key Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: VITE_USER_NODE_ENV Location: Package overview	Source	🚫
Dynamic require	npm/vite@4.0.1	Location: Package overview	Source	🚫
High entropy strings	npm/vite@4.0.1	Location: Package overview	Source	🚫
Filesystem access	npm/vite@4.0.1	Module: fs Location: Package overview	Source	🚫
Uses eval	npm/vite@4.0.1	Eval Type: Function Location: Package overview	Source	🚫
Dynamic require	npm/vite@4.0.1	Location: Package overview	Source	🚫
Network access	npm/vite@4.0.1	Module: net Location: Package overview	Source	🚫
Network access	npm/vite@4.0.1	Module: http Location: Package overview	Source	🚫
CVE	npm/vite@4.0.1	CVE: GHSA-c24v-8rfc-w8vw Vite dev server option server.fs.deny can be bypassed when hosted on case-insensitive filesystem (HIGH) Affected versions: >= 4.0.0, <= 4.5.1 Patched version: 4.5.2	Source	🚫
CVE	npm/vite@4.0.1	CVE: GHSA-353f-5xf4-qw67 Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//) (HIGH) Affected versions: >= 4.0.0, < 4.0.5 Patched version: 4.0.5	Source	🚫
Dynamic require	npm/vite@4.0.1	Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: TERM Location: Package overview	Source	🚫
Environment variable access	npm/vite@4.0.1	Env Vars: VITE_DEBUG_FILTER Location: Package overview	Source	🚫
Uses eval	npm/vite@4.0.1	Eval Type: Function Location: Package overview	Source	🚫
Shell access	npm/vite@4.0.1	Module: child_process Location: Package overview	Source	🚫
Debug access	npm/vite@4.0.1	Module: module Location: Package overview	Source	🚫
Network access	npm/vite@4.0.1	Module: https Location: Package overview	Source	🚫
Network access	npm/vite@4.0.1	Module: tls Location: Package overview	Source	🚫
Network access	npm/axios@1.7.4	Module: globalThis["fetch"] Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

What are high entropy strings?

Contains high entropy strings. This could be a sign of encrypted data, leaked secrets or obfuscated code.

Please inspect these strings to check if these strings are benign. Maintainers should clarify the purpose and existence of high entropy strings if there is a legitimate purpose.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/vue@3.3.4
• @SocketSecurity ignore npm/ws@8.12.0
• @SocketSecurity ignore npm/vue-eslint-parser@9.1.0
• @SocketSecurity ignore npm/vite@4.0.1
• @SocketSecurity ignore npm/axios@1.7.4