Skip to content

CVE-2009-3960

Unspecified vulnerability in BlazeDS 3.2 and earlier, as used in LiveCycle 8.0.1, 8.2.1, and 9.0, LiveCycle Data Services 2.5.1, 2.6.1, and 3.0, Flex Data Services 2.0.1, and ColdFusion 7.0.2, 8.0, 8.0.1, and 9.0, allows remote attackers to obtain sensitive information via vectors that are associated with a request, and related to injected tags and external entity references in XML documents.

CVSS
6.5Mediumscored by CISA
Exploited in the wild
Yes, in CISA KEV since 7 Mar 2022CISA deadline for US federal agencies: 7 Sept 2022known use in ransomware campaignspublic exploit code
EPSS
90.1%chance of exploitation in the next 30 daystop 0.3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
15 Feb 2010analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable
At runtime
Attack vector
network
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • adobe:blazeds
  • adobe:coldfusion
  • adobe:flex_data_services
  • adobe:livecycle
  • adobe:livecycle_data_services

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 7 Mar 2022. Known use in ransomware campaigns.
CISA due date
7 Sept 2022, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 2 on Exploit-DB · 1 Metasploit module
CISA SSVC
exploitation active, automatable no, technical impact partialAssessed by CISA 11 Mar 2022 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 15 Feb 2010Published
  2. 22 Feb 2010First public exploit or proof of concept6 days later
  3. 7 Mar 2022Added to CISA KEV (exploited in the wild)4,396 days (about 12 years) later
  4. 11 Mar 2022CISA SSVC assessment: exploitation active4 days later
  5. 7 Sept 2022CISA remediation due date (US federal agencies)180 days (about 6 months) later
  6. 6 Aug 2026CVE record last updated1,429 days (about 4 years) later
  7. 12 Nov 2026Analysed by vulneraibility.com98 days (about 3 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityNoneNo unauthorised modification.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2009-3960 being exploited?

Yes. CVE-2009-3960 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2009-3960?

CVE-2009-3960 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2009-3960?

Yes. A fix has been recorded for CVE-2009-3960. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2009-3960 affect?

CVE-2009-3960 affects adobe:blazeds, adobe:coldfusion, adobe:flex_data_services, adobe:livecycle, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

7 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

Exploits (1)

Other links (5)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com