CVE-2026-7049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe PixelYourSite Pro – Your smart PIXEL (TAG) Manager plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 12.5.0.1 via the scan_video. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The SSRF is blind because fetched response bodies are only parsed internally for YouTube/Vimeo patterns and are never returned to the attacker.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe PixelYourSite Pro WordPress plugin contains a blind SSRF vulnerability in the scan_video function, allowing unauthenticated attackers to make arbitrary HTTP requests from the server. While the attacker cannot see response bodies (they're internally parsed for YouTube/Vimeo patterns), the SSRF can probe internal services, interact with localhost interfaces, and potentially pivot to internal network attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PixelYourSite Pro plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate PixelYourSite Pro, or inspect the plugin directory /wp-content/plugins/pixelyoursite-pro/ for the main plugin fileAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionCheck the plugin header in pixelyoursite-pro.php or view the plugin details page in WordPress admin which displays the version numberAffected if Version is 12.5.0.1 or lower (the scan_video function vulnerability exists up to this version)
-
Confirm the video scanning feature is activeNavigate to PixelYourSite Pro settings > General or Video settings area and check if video tracking/scanning is enabled; also verify the endpoint /wp-admin/admin-ajax.php?action=scan_video is accessibleAffected if Video scanning feature is enabled and the scan_video AJAX endpoint is publicly accessible without authentication
-
Inspect server access logs for suspicious scan_video requestsReview web server access logs (Apache/Nginx) for requests to admin-ajax.php with action=scan_video parameters from unexpected IP addresses, especially those targeting internal IP ranges (10.x.x.x, 192.168.x.x, 127.0.0.1)Affected if Logs show requests to the scan_video endpoint targeting internal network addresses or localhost
You are affected if PixelYourSite Pro version 12.5.0.1 or lower is installed with the video scanning feature enabled, allowing unauthenticated blind SSRF attacks via the scan_video AJAX endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a version beyond 12.5.0.1 once available. Until patched, consider restricting access to the affected endpoint via WAF rules or temporarily disabling the plugin if the video scanning feature is not essential.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data