Pixelavo's public nonce lets visitors inject Facebook conversion events
Pixelavo before 1.5.4 registers an unauthenticated AJAX action whose nonce is published on every front-end page. Any visitor can obtain that nonce and submit attacker-controlled event data, which the plugin forwards to the configured Facebook Conversions API using the Administrator's stored access token. This can pollute advertising analytics and consume the account's API quota. The record does not disclose the action, nonce name, event fields or callback.
- Component
- Pixelavo
- Plugin slug
pixelavo- Affected
- < 1.5.4
- Safe version
1.5.4- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Pixelavo to 1.5.4 or later. Reconcile Facebook conversion events with real transactions, review public AJAX traffic for fabricated payloads, remove or annotate false events where supported, and rotate the stored Facebook access token if broader misuse is suspected.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Pixelavo WordPress plugin before 1.5.4 registers an unauthenticated AJAX action, gated only by a nonce that it emits publicly on every front-end page, that forwards client-supplied event data to the configured Facebook Conversions API using the administrator's stored access token. This allows an unauthenticated visitor to inject arbitrary conversion events into the administrator's Facebook ads account and exhaust the configured API quota.