CVE-2021-26722

The vuln CVE-2021-26722 has a tweet created 0 days ago and retweeted 10 times. /sec715/status/1358451170377801731 #S4wnugpxjc3al6

XSS In LinkedIn oncall (CVE-2021-26722) Poc: /query/<img src=x onerror=alert('xss')> Pic: https://t.co/5O6agyk154?amp=1

XSS In LinkedIn oncall (CVE-2021-26722) Poc: /query/<img src=x onerror=alert('xss')> Pic: https://t.co/5O6agyk154?amp=1

(Same from about 2 hours ago.) I think that the third retweeted(22 times) tweet that contains CVE ID between Feb 7 2021 09:01 UTC and Feb 8 2021 09:00 UTC is: /sec715/status/1358451170377801731 It has CVE-2021-26722. #l24_4wnugpxjc3al6

Top story: [CVE-2021-26722] Reflected Cross-Site Scripting in search bar. · Issue #341 · linkedin/oncall · GitHub https://t.co/2qr0QHbi6h?amp=1, see more https://t.co/fVnXn9Z0FJ?amp=1

I know no IPS that has a protection/signature/rule for the vulnerability CVE-2021-26722. The vuln was published 2 days ago by NIST. /search?src=sprv&q=CVE-2021-26722 #S4wnugpxjc3al6

(Same from about 4 hours ago.) I think that the third retweeted(22 times) tweet that contains CVE ID between Feb 7 2021 11:01 UTC and Feb 8 2021 11:00 UTC is: /sec715/status/1358451170377801731 It has CVE-2021-26722. #l24_4wnugpxjc3al6

(Same from about 2 hours ago.) I think that the second retweeted(27 times) tweet that contains CVE ID between Feb 7 2021 15:01 UTC and Feb 8 2021 15:00 UTC is: /sec715/status/1358451170377801731 It has CVE-2021-26722. #l24_4wnugpxjc3al6

(third → second) I think that the second retweeted(27 times) tweet that contains CVE ID between Feb 7 2021 13:01 UTC and Feb 8 2021 13:00 UTC is: /sec715/status/1358451170377801731 It has CVE-2021-26722. #l24_4wnugpxjc3al6