CVE-2025-48359
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in thaihavnn07 ATT YouTube Widget att-youtube allows Stored XSS.This issue affects ATT YouTube Widget: from n/a through <= 1.0.
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 · moderate confidenceA CSRF vulnerability in the ATT YouTube Widget allows attackers to inject malicious scripts (Stored XSS) by tricking authenticated administrators into submitting forged requests that modify the widget configuration with malicious payloads.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify if ATT YouTube Widget is installedSearch the plugin/module directory or application manifest for files related to 'att youtube widget' or 'ATT YouTube Widget'. Check the site's plugin list, theme functions, or component registry depending on the platform (WordPress, Joomla, etc.).Affected if The widget/plugin is present in the installation
-
Determine the installed version of the widgetLocate the widget's main file (often named similarly to the widget) and check the version header in the file comments, a version constant, or a changelog/readme file included with the widget package.Affected if The installed version cannot be determined or falls within an affected range (no specific safe version confirmed; treat all versions as potentially affected)
-
Verify admin access to widget settings existsNavigate to the widget configuration panel accessible via the CMS admin dashboard. Look for settings pages under Plugins, Widgets, or Components that control the YouTube widget parameters (API key, channel ID, display options, etc.).Affected if The admin settings panel for the widget is accessible and allows configuration changes
-
Inspect widget configuration for suspicious stored contentAccess the widget settings panel and examine all text fields (titles, descriptions, custom parameters) for unexpected JavaScript tags, event handlers, or encoded payloads that may indicate prior exploitation.Affected if Stored XSS payloads are present in any widget configuration field
-
Check for CSRF token validation on admin actionsReview the widget's source code for nonce validation or CSRF token checks on any PHP functions that handle form submissions or AJAX requests modifying widget settings. Search for 'nonce', 'verify_nonce', 'check_admin_referer', or similar validation calls.Affected if No CSRF token validation is found in the code handling widget configuration updates
The environment is affected if the ATT YouTube Widget is installed, its admin configuration interface is accessible, and the code lacks proper CSRF protection (nonce validation) on state-changing admin actions.
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 dataImplement anti-CSRF tokens (nonce validation) on all state-changing admin actions and apply proper output escaping/sanitization for the widget settings to prevent XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48359 — 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-2025-48359 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