Hello Guest, welcome to torrentinvites.org - Your #1 source for Torrent Invites!
CLICK HERE to register for free and gain full access to TI.org!
Torrent Invites! Buy, Trade, Sell Or Find Free Invites, For EVERY Private Tracker! HDBits.org, BTN, PTP, MTV, Empornium, Orpheus, Bibliotik, RED, IPT, TL, PHD etc!
-
WordPress Google Analytics Plugin by Yoast Vulnerable to critical site-hijacking
Yet another vulnerability has been found in the Yoast WordPress plugin that can be exploited by attackers allowing them to control the site.
Just a week ago, the case was associated with WordPress SEO plugin that is being used by more than a million WordPress websites. However, this time the case is focused on the company’s Google Analytics plugin that seems to have been downloaded for about 7 million times
Jouko Pynnonen from Finland is the researcher who has discovered the security flaw, says the vulnerability “allows an unauthenticated attacker to store arbitrary HTML, including JavaScript, in the WordPress administrator’s Dashboard on the target system. The JavaScript will be triggered when an administrator views the plug-in’s settings panel. No further user interaction is required.”
“Typically this can be used for arbitrary server-side code execution via the plugin or theme editors. Alternatively the attacker could change the administrator’s password, create new administrator accounts, or do whatever else the currently logged-in administrator can do on the target site,” he added.
The PoC for exploitation was also provided by Pynnonen since vulnerability has already been patched.
The flaw was revealed to Yoast on Wednesday, after which it release a new version (5.3.3) of the plug-in on Thursday. It is recommended that the user updated their plug-ins immediately.
Joost de Valk, the owner of Yoast told that there is no proof as to any incident that suggests the flaw had been exploited.
Google Analytics shows property names containing Javascript code and the list of profiles can prove to be really hazardous. The admin could be a victim of a harsh XSS attack when he/she visits the setting page because the company did not evade the property names on output properly. The attacker will find difficulty in automating this, however, if someone wanted to target someone else’s site, he/she could.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules