Skip to main content
VulnerabilityPublished

CVE-2025-12518: Bee Content Design Befree SDK · XSS or 'Cross-site Scripting'

Affects Bee Content Design Befree SDKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.47.0 when convenient.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.47.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Bee Content Design Befree SDK to 3.47.0.

Affected software

ProductAffectedFixed in
Bee Content DesignBefree SDKAffected
  • <3.47.0
Fixed in
  • 3.47.0

AI-suggested

Organizations should immediately update the Bee Content Design Befree SDK to version 3.47.0 or later, where this vulnerability is patched. If you cannot patch yet, restrict access to the email template preview functionality to trusted users only and monitor for unusual activity related to template creation or previewing. Implement additional input validation and output encoding on URL parameters, especially those controlling social media icon URLs, to prevent injection of malicious scripts. Review and strengthen the Content Security Policy to further restrict script execution, including disallowing inline scripts and limiting allowed sources. Conduct security training for developers and content creators to recognize and avoid injecting untrusted input into templates. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious payloads targeting the preview page. Finally, audit existing email templates for suspicious or unauthorized code injections and remove any malicious content.

Description

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.

References

Community reviews

Loading reviews…