LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0523: IBM WebSphere Commerce Enterprise 5.6.x through 5.6.1.5, 6.0.x through 6.0.0.11, and 7.0.x through 7.0.0.7...

IBM WebSphere Commerce Enterprise 5.6.x through 5.6.1.5, 6.0.x through 6.0.0.11, and 7.0.x through 7.0.0.7 does not use a suitable encryption algorithm for storefront web requests, which allows remote attackers to obtain sensitive information via a padding oracle attack that targets certain UTF-8 processing of the krypto parameter, and leverages unspecified browser access or traffic-log access.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-0523 affects legacy IBM WebSphere Commerce Enterprise storefronts. The product used unsuitable encryption for storefront web requests, which could let a remote attacker recover sensitive information through a padding oracle weakness involving the krypto parameter. The sources do not show active exploitation or a CVSS score. Exposure is most likely for organizations still running affected IBM WebSphere Commerce Enterprise versions on public storefronts or retaining request logs containing the vulnerable krypto parameter. Modern or upgraded deployments are not shown as affected in the provided bundle. High priority only if legacy IBM WebSphere Commerce Enterprise remains in use. The risk is sensitive data exposure from public commerce traffic, but evidence of current exploitation is absent in the supplied sources. Mitigation focus: Identify all IBM WebSphere Commerce Enterprise versions in production and archives.; Review IBM JR46386 and related IBM guidance for applicable fixes or upgrades.; Prioritize remediation for internet-facing storefronts handling customer or payment-adjacent data..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-0523 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.