As the blog with the images of Zuckerberg states, "It's time to fix those security flaws facebook..." 
 
 With Facebook under watch by the FTC for the next 20 years, we wonder what effect this will have on the social network considering that for every violation, the FTC could charge up to $16K. ][ UPDATE 11:52am PT: ] Facebook has ackowledged the bug that allowed users to access private photos and is currently fixing the bug. "Either they do not have any mandatory access control for private data, or someone approved of circumventing such access control measures for this feature. Facebook will then give you the option to help them take action by selecting additional photos to include in the report, which then gives you access to the user's private photos.  A Facebook security hole that allows you to view, save and share private photos has enabled one hacker to expose those of Mark Zuckerberg. Update: Facebook issued this statement a short time ago: 
 
 "Earlier today, we discovered a bug in one of our reporting flows that allows people to report multiple instances of inappropriate content simultaneously. Facebook added that the privacy of our user's data is a top priority for the company, and Facebook invests lots of resources in protecting our site and the people who use it.
– A temporary glitch allowed Facebook users to view others' private photos with a surprisingly easy trick, reports ZDNet. It's been fixed, but not before some of Mark Zuckerberg's own private photos got pilfered and reposted on blogs, like here at Launch. The trick: You could report an image to Facebook as inappropriate and mark the "nudity or pornography" box (even if it wasn't). At that point, Facebook would give you access to other photos in the user's private stream so you could check for more to flag. Facebook announced this afternoon that it fixed the problem, notes Gizmodo. "Earlier today, we discovered a bug in one of our reporting flows that allows people to report multiple instances of inappropriate content simultaneously," it said, calling the glitch "the result of one of our recent code pushes." The system has been disabled.