Skip to content

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Feb 11, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • php/razorpay_js/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Prototype Pollution
SNYK-JS-AXIOS-15252993
  710  

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:

🦉 Prototype Pollution

@snyk-io
Copy link
Author

snyk-io bot commented Feb 11, 2026

Merge Risk: Medium

This major version upgrade from axios 0.27.2 to 1.13.5 introduces some specific breaking changes, primarily in the v1.0.0 release. While the release aimed to modernize the library without major disruptions, there are behavioral changes that require verification.

Key Changes:

  • multipart/form-data Handling: The most significant change is how FormData payloads are handled. In versions before 1.x, axios would automatically set the Content-Type to multipart/form-data. In v1.x, if you manually set a different Content-Type header (e.g., application/json) on a request that has a FormData payload, axios may now attempt to serialize the FormData object to JSON, which will likely break the request.
  • Minor Changes: The upgrade also includes numerous bug fixes and security patches across the v1.x release series. No other major breaking API changes are documented for common use cases.

Recommendation:
Review any API calls that use FormData to ensure you are not manually setting a conflicting Content-Type header. If you are, the recommended action is to remove the manual header and allow axios to set it automatically.

Source: Community Migration Guide, Official Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@snyk-io
Copy link
Author

snyk-io bot commented Feb 11, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants