[Snyk] Security upgrade express from 4.18.2 to 4.21.2

[sumansaurabh]

User description

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

Snyk changed the following file(s):

• server/package.json
• server/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-8482416	721

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

---

Description

• Upgraded express from version 4.18.2 to 4.21.2 to address security vulnerabilities.
• Updated package-lock.json to reflect the changes in dependencies and their versions.
• This upgrade resolves a high severity vulnerability (ReDoS) identified by Snyk.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Update express dependency for security improvements            server/package.json Updated express dependency from 4.18.2 to 4.21.2. +1/-1      package-lock.json Update package-lock for express and dependencies                  server/package-lock.json Updated express version and other dependencies. Fixed vulnerabilities related to express. +276/-91

---

💡 Penify usage:
Comment /help on the PR to get a list of all available Penify tools and their descriptions

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are primarily version upgrades in package.json and package-lock.json, which are straightforward to review.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Suggest running tests after the upgrade to verify compatibility Consider running tests after upgrading the express package to ensure compatibility and functionality with the new version. server/package.json [4] -"express": "^4.21.2", +"express": "^4.21.2", // Ensure tests are run post-upgrade Suggestion importance[1-10]: 7 Why: The suggestion emphasizes the importance of testing after a package upgrade, which is a good practice for maintaining code stability, though it does not directly change the code itself.	7