Facebook Tool Lets Users Know if Their Photos Were Compromised in Latest Data Breach

Facebook Tool Lets Users Know if Their Photos Were Compromised in Latest Data Breach

Last week, Facebook reported using a software bug that affected nearly 7 million users, and also this bug may have subjected a broader set of photos to app developers than that which those users planned. The business has confirmed that the faulty API problem has been repaired, and that it’s also advised concerned third-party programmers to delete the photos. Developers will then have the ability to obtain access to this set of photos which would normally have been shared. Also, the business has also released a tool which will inform users if their information was compromised or not.
The brand new help page printed by Facebook will warn users whether their account has been compromised or not. This new page will need for you to be logged in to the social networking website. For users who have not suffered during the information breach, the following message displays,”Your Facebook accounts has not yet been affected by this issue and the apps you use didn’t have access to some other photographs.”

For those affected, the webpage will list all the apps where your photos were subjected to. In any case, even if your account’s photos have never been compromised, Facebook recommends logging in to some apps where you have shared with your Facebook photos to check which photographs they have access to, and invert it if an excessive amount of info has passed .

The company had previously said that only those people who granted permission for third-party programs to get the photos were changed. Generally, when people give programs access to their photographs, it means just photographs posted on their Facebook page. The insect affected photos that individuals uploaded into Facebook but decided not to post or couldn’t post for technical reasons.

Facebook explained that these users’ photos might have been exposed for 12 days in September (between September 13 and 25) and that the bug was repaired.


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.