WPIntell

Source evidence

Vulnerability- Admin+ Arbitrary File Clearing

Error Log Viewer by BestWebSoft · support · 2022-04-01T17:50:00+00:00

mixedsentiment
highseverity
0.88relevance
3replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Jon Brown resolved
I know this is a pretty trivial vulnerability limited to admin users, but it’s been showing up in the scanners for a long time and it’d be nice to not see it all the time 🙂 https://wpscan.com/vulnerability/166a4f88-4f0c-4bf4-b624-5e6a02e21fa0 Hi, All the vulnerabilities were fixed in the latest update. Can you confirm that the issue is reproducible in the latest version? The vulnerability report says this exists in versions <= 1.1.2. The latest version available on .org shows as 3 weeks old and v 1.1.2. This reply was modified 4 years, 1 month ago by Jon Brown . Hi, We have checked the report. The vulnerability was fixed in the latest version of the plugin, released on March 18. The last WordPress Scan check was on March 17. WordPress Scan may not have checked this vulnerability after March 17.

Comments

3 shown
andrewsupport 2022-04-04T11:40:00+00:00

Hi, All the vulnerabilities were fixed in the latest update. Can you confirm that the issue is reproducible in the latest version?

Jon Brown 2022-04-05T21:20:00+00:00

The vulnerability report says this exists in versions <= 1.1.2. The latest version available on .org shows as 3 weeks old and v 1.1.2. This reply was modified 4 years, 1 month ago by Jon Brown .

andrewsupport 2022-04-08T11:38:00+00:00

Hi, We have checked the report. The vulnerability was fixed in the latest version of the plugin, released on March 18. The last WordPress Scan check was on March 17. WordPress Scan may not have checked this vulnerability after March 17.