Potential fix for code scanning alert no. 3: Missing rate limiting

[kraftly-webstudio]

Potential fix for https://github.com/KraftlyWebStudio/MESSIA/security/code-scanning/3

In general, to fix missing rate limiting on an authorization-protected route, you should apply a suitable rate-limiting middleware (such as express-rate-limit) to that route or to a group of related routes. This ensures that expensive or security-sensitive operations cannot be abused through high-volume requests.

For this file, the best, least intrusive fix is to reuse the already defined authLimiter middleware on the /update route, just as is done for the /me route. This keeps behavior consistent, avoids introducing new dependencies or configurations, and does not change the business logic or the order of existing middlewares beyond inserting the limiter. Concretely, in apps/backend/routes/authRoute.js, on line 28 we change the route definition from authRouter.put("/update", authenticate, updateUserMiddleware, updateUserController); to include authLimiter directly after the path, e.g., authRouter.put("/update", authLimiter, authenticate, updateUserMiddleware, updateUserController);. No new imports or other definitions are required because authLimiter is already created in this file.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.