-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mongodb is vulnerable to SQL injection in PHP #1
Comments
I remember reading about this. I probably won't do any updates to Mongor from here on out, Laravel is going to be getting core MongoDB ORM support in the near future. Thanks! |
Thanks for the response... Where is a more detailed roadmap? Because http://laravel.com/roadmap says nothing about mongo support, or am i missing something? And btw, thanks for mongor. |
I just turned Mongor into a Eloquent-like ORM under the development branch, so I was thinking about this issue. I don't know if it's a good idea for me to force a string on the values because the developer building the application might not want a string. They might want another MongoID or an array. I am going to leave it up to them to force the right data until I can come up with a better way to do it and not limit the developer. Any ideas? |
why don't you include it as default option to mysql? with eloquent support. so people can just chose if its mysql or mongodb and use the same code... or at least similar code. |
Checkout; http://www.idontplaydarts.com/2010/07/mongodb-is-vulnerable-to-sql-injection-in-php-at-least/.. Should be a fairly simple fix.
The text was updated successfully, but these errors were encountered: