Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private details revealed in HTML source #30

Open
daamsie opened this issue Jan 19, 2022 · 0 comments
Open

Private details revealed in HTML source #30

daamsie opened this issue Jan 19, 2022 · 0 comments

Comments

@daamsie
Copy link

daamsie commented Jan 19, 2022

This was raised in a previous topic with a lack of resolution (but closed nonetheless).

The FB pixel rendered out in source looks like this:

<!-- End Facebook Pixel Code -->
<script type='text/javascript'>
  fbq('init', '<PIXEL_ID', {
    "em": "<EMAIL>",
    "fn": "<FIRSTNAME>",
    "ln": "<SURNAME>"
}, {
    "agent": "wordpress-5.8.3-3.0.6"
});
</script>

The email in question belongs to the user who is logged in. Harmless I hear you say because they already know their own email address.

However, a malicious browser extension could very easily harvest email addresses and the user’s private data this way.

Say I created a handy extension called “Tracking Pixel Detector” or some such that users could install to keep an eye on tracking pixels. Every site they visit where they are logged in will reveal their email address to the extension.

Please address this potential security hole by ensuring email addresses are NEVER displayed in the source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant