ContributionsMost RecentMost LikesSolutionsRe: Is community impacted by Log4J vulnerability? tywwrote: I think the issue you're seeing is related to Web Application Firewall (WAF) changes that may have been made on your site. We hit this with the word 'localhost'. No matter what we did, that word caused a 403 error. After checking in with Support they asked me to review the WAF email and sure enough that was the culprit. The 403 forbidden error is definitely because of the WAF, and rightly so! It's basically the 1st line of defense in preventing any kind of attack using the Log4Shell vulnerability. The WAF blocks "jndi" followed by ":" because that is a must in the string used to start the attack. So even if you have a vulnerable server, the server will not receive any malicious strings because you're blocking it before it even gets sent to the server. Re: Is community impacted by Log4J vulnerability? allisonablewrote: It appears to be some type of block on content related to the topic? It seems (after some trial and error) the phrase "jndi" plus ":" is being blocked by Khoros in all input forms generating a 403 forbidden error. Try removing that phrase from the topic (if it's in there at all)? Re: Security risk? Our search bar is being tested periodically for vulnerabilities FYI, we've also raised this question to Khoros directly and have received a comforting response: "We can confidently confirm that the mentioned query, although looks like SQL, is actually a Khoros(Lithium) specific language - LiQL which is well protected against most of common attacks like SQL injections. You can share a couple of articles to anyone who would want to understand the same with below links: 1. https://community.khoros.com/t5/Community-FAQ-s-from-Support/Is-LiQL-vulnerable-to-SQL-injection-attacks/ta-p/281334 2. https://community.khoros.com/t5/Developer-Discussion/LiQL-injection-attacks-and-quotes-in-Rest-API-2-0/m-p/231920"