Skip to main content
LowContentOWASP A05:2021CWE-200

How to fix: Ad-Tech Tracking Pixel on Login Page

An ad-tech tracking pixel (Meta, TikTok, Snap, or LinkedIn) was detected on a page that also contains a login form, increasing the third-party attack surface on a credential-entry page.

Why it matters

Any of these third-party scripts (or a compromised/malicious ad served through their network) executes in the same origin as the login form and can read or tamper with it, since the page grants them full script access.

Marketing pixels are designed to run on public marketing pages, not credential-entry surfaces. Every third-party script included on a login page is a script that, if compromised, can read the password field, inject a fake form, or exfiltrate credentials.

How to fix it

  1. 1Remove marketing/ad pixels from login, signup, and password-reset pages.
  2. 2If conversion tracking on signup is required, fire it from a post-login confirmation page instead.
  3. 3Restrict third-party script origins on auth pages via a strict Content-Security-Policy.

Code examples

Keep tracking pixels off auth routes

TypeScript
// Only load marketing pixels on public marketing routes,
// never on /login, /signup, or /reset-password
if (!pathname.startsWith('/login') && !pathname.startsWith('/signup')) {
  loadMarketingPixels();
}

References

Detected automatically by VulnRadar. The check id is third-party-tracker-on-login-page, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Ad-Tech Tracking Pixel on Login Page?
VulnRadar rates this low severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id third-party-tracker-on-login-page, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Ad-Tech Tracking Pixel on Login Page map to?
It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for ad-tech tracking pixel on login page

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Ad-Tech Tracking Pixel on Login Page | VulnRadar