Closed
Description
I've been struggling with a problem that appears to have been fixed in #47 as I'm running v1.0.0 of the wordpress-rule-exclusions-plugin
When I update to the HEAD of master, it fixes the problem.
I'm running libapache2-mod-security2 2.9.3-1ubuntu0.1
I have CRS ver.4.6.0-dev
Editing the footer of a wordpress theme triggers HTTP header is restricted by policy (/x-http-method-override/)
followed by a 5 more warnings
Matched Data: XSS data found within ARGS:content: <!-- wp:group {\\x22align\\x22:\\x22wide\\x22,\\x22layout\\x22:{\\x22type\\x22:\\x22constrained\\x22}} -->\\x0a<div class=\\x22wp-block-group alignwide\\x22><!-- wp:group {\\x22align\\x22:\\x22wide\\x22,\\x22style\\x22:{\\x22spacing\\x22:{\\x22padding\\x22:{\\x22top\\x22:\\x22var:preset|spacing|50\\x22,\\x22bottom\\x22:\\x22var:preset|spacing|50\\x22}}}} -->\\x0a<div class=\\x22wp-block-group alignwide\\x22 style=\\x22padding-top:var(--wp--preset--spacing--50);padding-bottom:var(--wp--pres...
NoScript XSS InjectionChecker: HTML Injection
Node-Validator Deny List Keywords
Inbound Anomaly Score Exceeded (Total Score: 20)
Anomaly Scores: (Inbound Scores: blocking=20, detection=20, per_pl=20-0-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=0, XSS=15, RFI=0, LFI=0, RCE=0, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=20)
Would it be possible to cut a new release with these fixes (just so others don't struggle trying to figure out why wordpress won't work with modsecurity)?
Metadata
Metadata
Assignees
Labels
No labels