dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-12518

MEDIUM · 5.3 CVSS v4.0 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
beefree.io SDK is vulnerable to Stored XSS in Social Media icon URL parameter in email builder functionality. Malicious attacker can inject arbitrary HTML and JS into template, which will be rendered/executed when visiting preview page. However due to beefree's Content Security Policy not all payloads will execute successfully. This issue has been fixed in version 3.47.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 · high confidence

The beefree.io SDK email builder contains a stored XSS vulnerability in the Social Media icon URL parameter. Attackers can inject malicious HTML/JavaScript into templates that execute when users visit the preview page. While Content Security Policy provides partial mitigation, the stored nature of the payload means it persists and executes for anyone viewing affected templates.

MitigationUpgrade beefree.io SDK to version 3.47.0 or later to receive the security patch. Additionally, review existing email templates for any malicious social media icon URLs that may have been injected prior to the upgrade.

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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify beefree.io SDK installation
    Search your codebase, dependencies (package.json, composer.json, requirements.txt), or application modules for 'beefree', 'bee-', or 'beemail' SDK references. Check any integrated email builder components.
    Affected if beefree.io SDK is present in your environment
  2. Determine installed SDK version
    Run a dependency query command (e.g., npm list beefree-sdk, pip show beefree, or equivalent for your package manager). Compare the version number to 3.47.0.
    Affected if The installed version is lower than 3.47.0
  3. Locate email template storage
    Identify where email templates are stored (database tables, file system, CMS content). Look for tables or files containing template data, particularly those with social media or icon configuration fields.
    Affected if You store or manage email templates created with beefree.io SDK
  4. Inspect social media icon URL fields
    Query template storage for any fields related to social media icons (e.g., social_icon_url, social_links, icon_facebook, icon_twitter, etc.). Examine the stored URLs for suspicious patterns like javascript:, data:, or unusual domain names.
    Affected if Any templates contain unexpected or malicious URLs in social media icon fields
  5. Review template preview functionality
    If your system has a template preview feature, test it with a template containing social media icons. Observe if the preview page renders the icon URLs without sanitization.
    Affected if Social media icon URLs execute as HTML or JavaScript in the preview
  6. Audit recent template changes
    Review template modification logs, audit trails, or version history for recent changes to social media icon URLs, especially those added by users with elevated privileges or unknown sources.
    Affected if Templates contain social media icon URLs that were modified recently and contain suspicious content

Your environment is affected if beefree.io SDK version is below 3.47.0 AND any stored email templates contain malicious social media icon URL payloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade beefree.io SDK to version 3.47.0 or later to receive the security patch. Additionally, review existing email templates for any malicious social media icon URLs that may have been injected prior to the upgrade.

Recommended fix High confidence

3.47.0

  1. Upgrade the beefree.io SDK to version 3.47.0 or later to resolve the Stored XSS vulnerability in the Social Media icon URL parameter

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12518 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12518 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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