Skip to content

CVE-2010-2075

UnrealIRCd 3.2.8.1, as distributed on certain mirror sites from November 2009 through June 2010, contains an externally introduced modification (Trojan Horse) in the DEBUG3_DOLOG_SYSTEM macro, which allows remote attackers to execute arbitrary commands.

CVSS
7.5High
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
83.5%chance of exploitation in the next 30 daystop 0.4% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
15 Jun 2010analysed here 12 Nov 2026

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-20 Improper Input Validation
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

  • unrealircd:unrealircd

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
Not listed as of our last sync.
Public exploit code
Yes: 2 on Exploit-DB · 1 Metasploit module · 11 GitHub proofs of concept

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. 13 Jun 2010First public exploit or proof of concept
  2. 15 Jun 2010Published3 days later
  3. 7 Aug 2024CVE record last updated5,167 days (about 14 years) later
  4. 12 Nov 2026Analysed by vulneraibility.com827 days (about 2 years) later

CVSS vector

CVSS 2.0 · AV:N/AC:L/Au:N/C:P/I:P/A:P

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.

Common questions

Is CVE-2010-2075 being exploited?

Not confirmed. CVE-2010-2075 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 84% probability of exploitation in the next 30 days.

How severe is CVE-2010-2075?

CVE-2010-2075 is rated High with a CVSS score of 7.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-2010-2075?

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

What does CVE-2010-2075 affect?

CVE-2010-2075 affects unrealircd:unrealircd. 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

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

Advisories (2)

Exploits (1)

Other links (7)

Show 1 more

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