CVE-2025-53041
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 · uneditedVulnerability in the Oracle iStore product of Oracle E-Business Suite (component: Shopping Cart). Supported versions that are affected are 12.2.5-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle iStore. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle iStore, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle iStore accessible data as well as unauthorized read access to a subset of Oracle iStore accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
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 confidenceThis is an unauthenticated vulnerability in Oracle iStore's Shopping Cart component of Oracle E-Business Suite (versions 12.2.5-12.2.14). Attackers with network access can partially read and modify accessible data through the shopping cart functionality without credentials, but the attack requires human interaction from a victim. The scope change indicates successful attacks may impact additional Oracle products beyond iStore.
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>= 12.2.5, <= 12.2.14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Oracle E-Business Suite installationLocate Oracle E-Business Suite installation directories or check Oracle Inventory for EBS components. Common paths include $ORACLE_HOME/apps or review opatch inventory outputs.Affected if Oracle E-Business Suite is installed and the version falls within 12.2.5 to 12.2.14 inclusive
-
Confirm iStore module is configuredCheck if the iStore module is enabled within Oracle E-Business Suite. This can be verified through Oracle Applications Manager (OAM) or by querying the FND_APPLICATION or ICX_SESSIONS tables in the EBS database.Affected if iStore module is installed and enabled in the EBS environment
-
Determine exact iStore versionQuery the Oracle database for iStore version information, typically found in version tables or through the iStore administrator interface. Compare the version number against the affected range 12.2.5 through 12.2.14.Affected if iStore version is 12.2.5, 12.2.6, 12.2.7, 12.2.8, 12.2.9, 12.2.10, 12.2.11, 12.2.12, 12.2.13, or 12.2.14
-
Verify iStore network accessibilityReview network configuration to determine if the iStore shopping cart URLs are exposed to untrusted networks. Check web server or load balancer configurations for iStore endpoints (typically /shopping/ or /ibshop/).Affected if iStore shopping cart functionality is accessible from untrusted network locations without authentication
The environment is affected if Oracle E-Business Suite with iStore version 12.2.5 through 12.2.14 is installed, the iStore module is enabled, and the shopping cart is network-accessible to untrusted 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 dataApply Oracle Critical Patch Updates for Oracle E-Business Suite when released, and restrict network access to iStore to minimize exposure until a patch is available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53041 — 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-53041 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