Drupal Symfony Mailer LiteDrupal extension · Drupal Symfony Mailer Lite Project
CVE-2024-13250
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 Drupal Drupal Symfony Mailer Lite allows Cross Site Request Forgery.This issue affects Drupal Symfony Mailer Lite: from 0.0.0 before 1.0.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Drupal Symfony Mailer Lite module allows attackers to trick authenticated users into performing unintended actions, such as modifying email configuration settings. The lack of proper CSRF token validation on module forms enables malicious requests to be executed without the user's consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Drupal Symfony Mailer LiteDrupal extension
< 1.0.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Drupal Symfony Mailer Lite module is installedIn the Drupal admin interface, navigate to Extend or use drush pm-list --type=module to list installed modules. Look for 'Symfony Mailer Lite' or 'symfony_mailer_lite' in the list.Affected if The module is not present in the installation list, then the site is not affected by this specific vulnerability.
-
Determine the installed version of the Symfony Mailer Lite moduleIn Drupal admin, go to Extend and find the Symfony Mailer Lite module to view its version number. Alternatively, check the module's info.yml file (modules/symfony_mailer_lite/symfony_mailer_lite.info.yml) or run: drush pm:list --filter=symfony_mailer_liteAffected if The installed version is less than 1.0.6, indicating the module lacks the CSRF protection fix.
-
Confirm module is enabled and accessibleCheck that the Symfony Mailer Lite module shows as 'Enabled' in Drupal's Extend page. Also verify the module configuration page is accessible at /admin/config/system/symfony_mailer_lite or similar path.Affected if The module is enabled and its configuration forms are accessible, meaning the CSRF-vulnerable forms can be targeted.
-
Inspect form configuration for CSRF token presence (optional advanced check)Examine the module's form handlers (usually in src/Form/ directory) for the presence of CSRF token validation using Drupal's FormBuilder or token services. Look for '::csrfToken' or '#token' in form definitions.Affected if Form definitions lack CSRF token validation (token generation and verification), indicating the vulnerability is present.
A Drupal site is affected if the Symfony Mailer Lite module is installed and enabled with a version lower than 1.0.6, allowing CSRF attacks on module configuration forms.
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.
dbcve · scoped1.0.6
Update Drupal Symfony Mailer Lite to version 1.0.6 or later to obtain the CSRF protection fix. Verify all module-related forms include proper token validation after the update.
1.0.6
- Upgrade Drupal Symfony Mailer Lite module to version 1.0.6 or later
- After upgrading, clear Drupal cache to ensure the new version is properly loaded
- Verify the fix by confirming the module version in the Drupal administration interface
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal Symfony Mailer Lite
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13250 — 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-2024-13250 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