Zum Inhalt springen

Archiv für das Tag "Security"

Wired: Facebook bug could have let advertisers get your phone number

Facebook tells users that giving the company their mobile phone number will help keep their account secure. Until a few weeks ago, however, the social network’s self-service ad-targeting tools could be massaged into revealing a Facebook user’s cellphone number from their email address. The same flaw made it possible to collect phone numbers for Facebook users who had visited a particular webpage.wired.com

Oh wow. This is why I was very reluctant to give platforms access to my phone number, and still have a bad feeling for the few where I enabled 2fa with a phone ...

WordPress 4.9.1 Security Update

WordPress versions 4.9 and earlier are affected by four security issues which could potentially be exploited as part of a multi-vector attack. As part of the core team's ongoing commitment to security hardening, the following fixes have been implemented in 4.9.1:

Use a properly generated hash for the newbloguser key instead of a determinate substring.

Add escaping to the language attributes used on html elements.

Ensure the attributes of enclosures are correctly escaped in RSS and Atom feeds.

Remove the ability to upload JavaScript files for users who do not have the unfiltered_html capability.


WordPress 4.7.5 Security and Maintenance Release

WordPress Logo an die VW-Fabrik gephotoshopped

Ladies and Gentlemen, start your update engines:

WordPress versions 4.7.4 and earlier are affected by six security issues:
Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing.
Improper handling of post meta data values in the XML-RPC API. Reported by Sam Thomas.
Lack of capability checks for post meta data in the XML-RPC API. Reported by Ben Bidner of the WordPress Security Team.
A Cross Site Request Forgery (CRSF) vulnerability was discovered in the filesystem credentials dialog. Reported by Yorick Koster.
A cross-site scripting (XSS) vulnerability was discovered when attempting to upload very large files. Reported by Ronni Skansing.
A cross-site scripting


WordPress 4.7.3 Security and Maintenance Release

Gerade eben scheint die neue Aktualisierung von WordPress auszurollen; mehrere meiner WP Installationen melden sich im Stromposteingang mit entsprechendem Hinweis auf das gerade erfolgte Update. Wieder wurden Sicherheitslücken gefunden und geschlossen und ein bisschen aufgeräumt.

This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

WordPress versions 4.7.2 and earlier are affected by six security issues:
Cross-site scripting (XSS) via media file metadata. Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs.
Control characters can trick redirect URL validation. Reported by Daniel Chatfield.
Unintended files can be deleted


WordPress 4.7.2 Security Release

WordPress versions 4.7.1 and earlier are affected (…):
The user interface for assigning taxonomy terms in Press This is shown to users who do not have permissions to use it. (…)
WP_Query is vulnerable to a SQL injection (SQLi) when passing unsafe data. WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. (…)
A cross-site scripting (XSS) vulnerability was discovered in the posts list table. (…)
An unauthenticated privilege escalation vulnerability was discovered in a REST API endpoint (…)
An additional serious vulnerability was fixed in this release and


WordPress 4.7.1 Security Update

Neues Jahr, neues Update – es sind Lücken gefunden und geschlossen worden, und ein bisschen aufgeräumt wurde auch unter dem Blogsofa, also ran an die Updateknöpf - egal, ob nun per Download und FTP, spooky WordPress Auto-Update oder per abgefahrenem Eigenbau.

WordPress versions 4.7 and earlier are affected by eight security issues:

Remote code execution (RCE) in PHPMailer – No specific issue appears to affect WordPress or any of the major plugins we investigated but, out of an abundance of caution, we updated PHPMailer in this release. This issue was reported to PHPMailer by Dawid Golunski and


Advice for Companies Fighting Ad Blockers - TJ van Toll

(…) Publishers that believe they can convince ad blocker users to turn off a tool that protects their privacy and data plans need to realize they’re on the wrong side of history. Respect your users or you’ll lose them.

WordPress 4.5.3 Security Release

WordPress Logo an die VW-Fabrik gephotoshopped

Gestern abend ist eine neue Version mit Sicherheits- und Wartungsfixes erschienen. Bei den diversen Installationen, in die ich involviert bin, hat sich das automatisch aktualisiert, auch bei älteren Versionen als 4.5.2, wie gehabt gibt es die Source aber auch zum Download auf wordpress.org.

WordPress versions 4.5.2 and earlier are affected by several security issues: redirect bypass in the customizer, reported by Yassine Aboukir; two different XSS problems via attachment names, reported by Jouko Pynnönen and Divyesh Prajapati; revision history information disclosure, reported independently by John Blackbourn from the WordPress security


WordPress 4.5.2 Security Update

WordPress Logo an die VW-Fabrik gephotoshopped

Heute Nacht ist ein neues Sicherheitsupdate für WordPress erschienen und hat sich hier bei mir auch auf diversen Seiten selbst aktualisiert:

WordPress versions 4.5.1 and earlier are affected by a SOME vulnerability through Plupload, the third-party library WordPress uses for uploading files. WordPress versions 4.2 through 4.5.1 are vulnerable to reflected XSS using specially crafted URIs through MediaElement.js, the third-party library used for media players. MediaElement.js and Plupload have also released updates fixing these issues.