LiveActive security incident?Get immediate response
CVE Record

CVE-2010-4660: Unspecified vulnerability in statusnet through 2010 due to the way addslashes are used in SQL string escapes..

Unspecified vulnerability in statusnet through 2010 due to the way addslashes are used in SQL string escapes..

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2010-4660 concerns StatusNet through 2010. The public bundle says the issue relates to using addslashes for SQL string escaping, but does not provide severity, CVSS, exploit status, or fixed versions. Treat this mainly as legacy exposure: any remaining StatusNet deployment should be identified and reviewed against vendor or Debian guidance.

Executive priority

Set priority based on asset presence. If no StatusNet exists, no action beyond documentation is needed. If StatusNet through 2010 is still running, treat it as a legacy application risk requiring prompt verification, upgrade, isolation, or retirement.

Technical view

The vulnerability is unspecified beyond unsafe SQL string escaping behavior involving addslashes in StatusNet through 2010. The source bundle provides no CWE, CVSS vector, affected CPEs, patch version, or exploit details. The most defensible assessment is a possible SQL handling weakness in legacy StatusNet code that requires version and package verification.

Likely exposure

Exposure is most likely limited to organizations still running StatusNet versions through 2010. Evidence is insufficient to name downstream packages, forks, hosted services, or exact vulnerable builds beyond the affected product statement in the CVE bundle.

Exploitation context

The bundle does not indicate active exploitation, and KEV is false. No public exploit status, exploit maturity, or attacker prerequisites are provided. Because the issue involves SQL string escaping, researchers should treat database-facing input paths as areas for controlled validation only.

Researcher notes

The record is sparse: no CVSS, CWE, fixed version, or exploit confirmation is included. Do not overstate severity. Focus research on confirming installed versions, locating authoritative package status, and reviewing SQL escaping paths without publishing weaponized details.

Mitigation direction

  • Inventory any StatusNet deployments and record exact versions.
  • Check CVE Program, Debian tracker, and vendor guidance for fixed package information.
  • If running StatusNet through 2010, prioritize upgrade or retirement planning.
  • Restrict public access to legacy StatusNet instances where business need is unclear.
  • Review database logs for unusual errors or unexpected query behavior.

Validation and detection

  • Confirm whether StatusNet is present in asset and package inventories.
  • Verify deployed versions against the CVE affected range: through 2010.
  • Review Debian tracker and vendor/community advisories for package-specific status.
  • Assess whether exposed StatusNet instances handle untrusted user input.
  • Document any uncertainty where version or patch evidence is unavailable.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2010-4660 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
statusnetstatusnetthrough 2010Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.