CVE-2013-6722
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 · uneditedUnrestricted file upload vulnerability in the Registration/Edit My Profile portlet in IBM WebSphere Portal 7.x before 7.0.0.2 CF27 and 8.x through 8.0.0.1 CF09 allows remote attackers to cause a denial of service or modify data via unspecified vectors.
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 · moderate confidenceUnrestricted file upload vulnerability in the Registration/Edit My Profile portlet of IBM WebSphere Portal allows remote attackers to upload unspecified files, potentially causing denial of service or enabling data modification. The vulnerability affects versions 7.x before 7.0.0.2 CF27 and 8.x through 8.0.0.1 CF09.
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= 7.0.0.0= 7.0.0.1= 7.0.0.2= 8.0= 8.0.0.0= 8.0.0.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/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 installed WebSphere Portal versionAccess the WebSphere Portal administration console or check the version information via the portal's About page (typically at /portal/about). The version number is displayed on the main dashboard or in the System Information section.Affected if The installed version is 7.0.0.0, 7.0.0.1, 7.0.0.2, 8.0, 8.0.0.0, or 8.0.0.1, or any 7.x version before 7.0.0.2 CF27, or 8.x through 8.0.0.1 CF09.
-
Confirm the portal is running version 7.x or 8.xVerify the major version number from the installation directory or administration interface. WebSphere Portal 7.x and 8.x store version metadata in the InstallationManager or portal root directory.Affected if The portal major version is 7 or 8.
-
Check if Registration portlet is deployedLog into the WebSphere Portal admin console and navigate to the Portlet Management section. Look for 'Registration' portlet or 'Edit My Profile' portlet in the list of deployed portlets.Affected if The Registration or Edit My Profile portlet is present and enabled on the portal.
-
Verify file upload capability on the profile portletAccess the user profile or registration page as an end user. Look for any file upload or attachment fields in the profile editing or registration forms.Affected if File upload fields are available in the Registration or Edit My Profile interface.
A user is affected if they run IBM WebSphere Portal versions 7.0.0.0 through 7.0.0.2 (before CF27) or 8.0.0.0 through 8.0.0.1 (before CF09) and have the Registration or Edit My Profile portlet enabled with file upload functionality accessible to users.
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 IBM WebSphere Portal 7.0.0.2 CF27 or later, or 8.0.0.1 CF09 or later. Additionally, implement strict file type validation and size limits on the Registration/Edit My Profile portlet.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6722 — 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-2013-6722 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