CVE-2006-7223
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 · uneditedPreviewAction in XWiki 0.9.543 through 0.9.1252 does not set the Author field to the identity of the user who last modified a document, which allows remote authenticated users without programming rights to execute arbitrary code by selecting a document whose author has programming rights, modifying this document to contain a script, and previewing without saving the document.
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 confidenceThe PreviewAction in XWiki versions 0.9.543-0.9.1252 fails to update the Author field when a user without programming rights previews a modified document. This allows authenticated users to inherit the programming permissions of the original document author during preview, enabling arbitrary code execution by embedding scripts in documents owned by users with programming rights.
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= 0.9.543= 0.9.790= 0.9.793= 0.9.840= 0.9.1252CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 XWiki versionAccess the XWiki administration panel or check the xwiki/WEB-INF/version.properties file to determine the installed version numberAffected if The installed version matches 0.9.543, 0.9.790, 0.9.793, 0.9.840, or 0.9.1252, or falls within the range 0.9.543 to 0.9.1252
-
Verify user programming rights statusLog in as the user account in question and check the user permissions profile, or query the database table xwikidoc for users with 'admin' or 'programming' rights grantedAffected if The user account lacks programming rights but has authenticated access to the wiki
-
Confirm PreviewAction is accessibleAttempt to access the preview function by modifying a document and clicking preview, or inspect the struts configuration files in xwiki/WEB-INF/struts-config.xml to verify the PreviewAction mapping exists and is not restrictedAffected if The PreviewAction is enabled and reachable by users without programming rights
-
Inspect document author inheritanceCreate a test document owned by a programming rights user, modify it as a non-programming user, preview the document, and verify the author field remains unchanged from the original owner rather than updating to the previewing userAffected if The author field retains the original document owner's identity after a non-programming user previews modifications
A user is affected if running a vulnerable XWiki version (0.9.543-0.9.1252) where the PreviewAction permits authenticated users without programming rights to preview documents while inheriting the original author's programming permissions.
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.
From vendor dataUpgrade to a patched XWiki version. If unable to upgrade immediately, disable or restrict the PreviewAction feature for users without programming rights, and review existing documents with programming rights authors for unauthorized modifications.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-7223 — 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-2006-7223 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