CVE-2025-30718
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 Applications Framework product of Oracle E-Business Suite (component: Attachments, File Upload). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Applications Framework accessible data as well as unauthorized read access to a subset of Oracle Applications Framework accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 access control vulnerability in the Attachments/File Upload component of Oracle Applications Framework (E-Business Suite 12.2.3-12.2.14). Low-privileged users can exploit the flaw via HTTP to achieve unauthorized read and write access to certain application data, indicating a broken access control or path traversal issue in the file upload functionality.
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.3, <= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Applications Framework versionQuery the Oracle database or check the environment for the Oracle EBS version (look for FND_PRODUCT_GROUPS or equivalent version tables). Use: SELECT release_name FROM fnd_product_groups; or check the EBS banner page.Affected if The installed version is between 12.2.3 and 12.2.14 inclusive.
-
Confirm the Attachments component is enabledCheck if the Attachments (FND_ATTACH) functionality is configured and enabled in the EBS instance. Look for active attachment entities and functions in the Oracle Forms/HTML pages.Affected if Attachments/File Upload component is actively configured and accessible to users.
-
Identify file upload endpointsReview the Oracle Applications Framework web tier configuration and locate URLs related to file uploads (typically under /OA_HTML/ or /oa_servlets/ paths). Check web.xml and Oracle HTTP Server configuration.Affected if File upload servlet endpoints are accessible via HTTP without additional authentication layers.
-
Verify access control on upload functionalityTest the file upload functionality with a low-privileged user account (limited to standard responsibilities). Attempt to access upload features or upload files to restricted directories via the Attachments component.Affected if Low-privileged users can access or exploit the file upload functionality to read/write to locations outside their authorized scope.
-
Review HTTP access logs for upload anomaliesExamine web server access logs (OHS/Apache logs in $ORACLE_HOME/instance/frontend/OHS/ohs1/logs) for unusual file upload POST requests, especially those targeting unexpected paths or repeated upload attempts by low-privilege users.Affected if Logs show file upload requests from low-privileged users to paths or resources they should not have access to.
You are affected if Oracle Applications Framework version 12.2.3 through 12.2.14 is installed AND the Attachments/File Upload component is enabled and accessible to low-privileged users via HTTP.
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 Oracle's Critical Patch Update (CPU) containing the CVE-2025-30718 fix for Oracle Applications Framework. Until patched, restrict network access to the EBS interfaces and monitor for anomalous file upload patterns.
- Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-30718. Check Oracle's April 2025 CPU or subsequent CPU for the patch specific to Oracle Applications Framework.
- Verify the patch applies to Oracle E-Business Suite version 12.2.3 through 12.2.14.
- After applying the patch, restart the affected application services as instructed in the patch readme.
- Confirm the patch was successfully applied by reviewing the applied patches list using Oracle AD Patch utility.
- Validate that the Attachments/File Upload functionality works correctly after the patch.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.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,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30718 — 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-30718 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