CVE-2021-47711
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 · uneditedA SQL injection vulnerability in Kentico Xperience allows authenticated editors to inject malicious SQL queries via online marketing macro method parameters. This enables unauthorized database access and potential data manipulation by exploiting macro method input validation weaknesses.
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 confidenceSQL injection vulnerability in Kentico Xperience CMS allows authenticated editor-level users to inject malicious SQL queries through online marketing macro method parameters due to insufficient input validation. The weakness in macro method handling permits attackers to manipulate database queries, potentially enabling unauthorized data access or modification.
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<= 13.0.52CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed Kentico Xperience versionCheck the Kentico Xperience version through the administration interface (typically found in the 'About' section of the CMS Desk or via the system DLL version information)Affected if The installed version is 13.0.52 or lower (any version <= 13.0.52)
-
Confirm online marketing macro functionality is in useReview whether the Kentico Xperience instance utilizes online marketing features that involve macro methods, particularly custom or third-party macros that accept user input as parametersAffected if Online marketing macros are configured and accessible within the CMS
-
Audit user accounts with editor-level permissionsReview the user roles and permissions in the Kentico Xperience administration under 'Users' and 'Roles', specifically looking for accounts granted editor-level accessAffected if There are active user accounts with editor-level permissions who can access and execute macro methods
-
Check for macro execution logs or audit trailsExamine Kentico Xperience event logs and macro execution logs (if available) for any suspicious macro method calls with unusual parameter patternsAffected if There are macro execution records showing unusual or potentially malicious parameter values
-
Inspect custom macro method implementationsReview any custom macro definitions in the CMS, particularly those handling database queries or accepting external input through online marketing featuresAffected if Custom macros exist that accept parameters and interact with database queries without proper sanitization
The environment is likely affected if running Kentico Xperience version 13.0.52 or lower with online marketing macros enabled and editor-level user accounts present.
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 · scopedApply the vendor-supplied patch or upgrade to a fixed Kentico Xperience version that addresses macro method input validation. Review user permissions for macro execution and consider additional input sanitization as a defense-in-depth measure.
Kentico Xperience 13.0.53 or later (latest available 13.0.x hotfix)
- 1. Back up your current Kentico Xperience database and application files.
- 2. Download the latest Kentico Xperience 13.0 hotfix from the Kentico DevNet portal (login required) or from the Kentico download page.
- 3. Apply the hotfix by running the installer or extracting the hotfix package to your Xperience installation directory.
- 4. Run the installation process which will update the database schema if required.
- 5. Verify the fix by testing the online marketing macro functionality that was vulnerable.
- 6. Clear application caches and restart the IIS application pool.
- 7. Confirm the application runs without errors after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47711 — 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-2021-47711 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