CVE-2025-52122
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 · uneditedFreeform 5.0.0 to before 5.10.16, a plugin for CraftCMS, contains an Server-side template injection (SSTI) vulnerability, resulting in arbitrary code injection for all users that have access to editing a form (submission title).
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 confidenceFreeform plugin for CraftCMS versions 5.0.0 through 5.10.15 contain a server-side template injection (SSTI) vulnerability in the form submission title field. Users with permission to edit forms can inject arbitrary code through the submission title, leading to remote code execution on the server.
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>= 5.0.0, < 5.10.16CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Check installed Freeform plugin versionIn the CraftCMS control panel, go to Settings > Plugins and locate Freeform to see the version number. Alternatively, check the composer.json file in the project root for 'solspace/freeform' under 'require'Affected if Version is 5.0.0 through 5.10.15 (any version >= 5.0.0 and < 5.10.16)
-
Confirm form editing permissions existIn CraftCMS, go to Settings > Users > Groups or individual user settings and verify if any user group or user has permission to edit forms (typically 'Solspace Freeform - Forms - Edit' or similar permission)Affected if Any user account has form editing permissions enabled, especially if accessible to non-admin users
-
Verify Freeform form submissions are in useIn the CraftCMS control panel, navigate to Freeform > Submissions to see if there are any form submissions stored in the systemAffected if Submissions exist and the form submission title field is being used, as this is the injection point for the SSTI
You are affected if the Freeform plugin version is 5.0.0 through 5.10.15 AND any user with form editing permissions can submit forms with a crafted title containing template code.
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 · scoped5.10.16
Upgrade Freeform plugin to version 5.10.16 or later. Immediately review user permissions for form editing access until the patch is applied.
Freeform 5.10.16
- Backup your CraftCMS database and files before proceeding with any updates
- Update Freeform to version 5.10.16 or later via Composer (composer update solspace/freeform) or through the Craft CMS plugin store
- Clear all CraftCMS caches after the upgrade to ensure the new version is fully active
- Verify the upgrade was successful by checking the Freeform version in the control panel
- Test form submission functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52122 — 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-52122 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