Skip to main content
Mallory
MediumVulnerability

CVE-2009-1968: XSS in Oracle Secure Enterprise Search (search_p_groups parameter)

Published Jul 14, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS40.1%99th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Oracle Corporation
IdentifiersCVE-2009-1968CWE-79

CVE-2009-1968 is a vulnerability in the Secure Enterprise Search component of Oracle Database 10.1.8.3. It allows remote attackers to affect the integrity of the application, reportedly via a cross-site scripting (XSS) vector involving the search_p_groups parameter in the search/query/search endpoint. The vulnerability could allow an attacker to inject arbitrary web script or HTML into the context of a user's browser session.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary JavaScript in the context of a user's session, potentially leading to session hijacking, credential theft, or other attacks that compromise the integrity of user data and application state.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, restrict access to the vulnerable search/query/search endpoint, sanitize user input for the search_p_groups parameter, and employ web application firewalls (WAFs) to filter malicious input until the official patch can be applied.

Remediation

Patch, then assume compromise.

Apply the relevant patches provided by Oracle in the July 2009 Critical Patch Update (CPU) for Oracle Database 10.1.8.3. Ensure all systems are updated to the latest secure version.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationDatabase Serverapplication
FAQ

Frequently asked questions

Is CVE-2009-1968 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-1968 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-1968?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-1968. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-1968?
Apply the relevant patches provided by Oracle in the July 2009 Critical Patch Update (CPU) for Oracle Database 10.1.8.3. Ensure all systems are updated to the latest secure version.
What products are affected by CVE-2009-1968?
Oracle Corporation Database Server.
How severe is CVE-2009-1968?
CVE-2009-1968 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 40.1% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.