CVE-2026-21943: Oracle Scripting · Cross-site Scripting
Affects Oracle ScriptingSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationOracle Scripting | Affected
| Fixed in– |
Mavencom.oracle/OracleScriptingpkg:maven/com.oracle/OracleScriptingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor Oracle’s official security advisories closely and apply patches or updates as soon as they become available for Oracle Scripting and related components. 2. Restrict network access to Oracle Scripting interfaces by implementing network segmentation and firewall rules to limit exposure to trusted hosts only. 3. Enhance user training and awareness programs to reduce the risk of successful social engineering attacks that could trigger the required user interaction. 4. Implement multi-factor authentication (MFA) where possible to add an additional layer of security for users interacting with Oracle E-Business Suite. 5. Conduct regular audits and monitoring of Oracle Scripting data access and modification logs to detect anomalous activities promptly. 6. Employ web application firewalls (WAF) to detect and block suspicious HTTP requests targeting Oracle Scripting endpoints. 7. Review and minimize privileges granted to Oracle Scripting users and service accounts to limit potential damage from unauthorized access. 8. Consider deploying endpoint protection solutions that can detect phishing attempts and malicious payloads that might be used to facilitate the required user interaction.
Description
Vulnerability in the Oracle Scripting product of Oracle E-Business Suite (component: Scripting Admin). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Scripting. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Scripting, 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 Scripting accessible data as well as unauthorized read access to a subset of Oracle Scripting 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).