Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
IBResource ltd. Posted May 17, 2022 Posted May 17, 2022 When using loose profanity filter with "Block submission" action it works not as expected because of js regexp. reggie = new RegExp("(?:\\b|\\s|^)(" + looseWords.join('|') + "\\w*)(?:\\b|\\s|$)","ig"); At first it only find words starting with filter. If i try to filter "word" it match "wordpress" but not "sword". Secondly "\w" does not match non-latin word characters but "\b" includes non-latin letters in opposite. In last js filters content on browser side only and there is no content validation in php backend when using "Block submission" option. So it's easy to prevent filtering by devtools in browser and post bad words out of control.
Jim M Posted May 18, 2022 Posted May 18, 2022 Please be advised that I have tagged this to a developer for further review. Someone will be with you as soon as they can.
Management Solution Matt Posted May 18, 2022 Management Solution Posted May 18, 2022 Thanks for letting us know. This should be fixed in the June release. SeNioR- 1
Recommended Posts