dbcve.org
StatusnetApplication · Status

CVE-2010-4660

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-20
Fix available
A fix is available. Upgrade to after 2010 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in StatusNet (through 2010) caused by improper use of addslashes() for SQL string escaping. The addslashes() function is not safe for database escaping (especially with certain character encodings), allowing attackers to bypass the escaping and inject malicious SQL queries.

MitigationReplace all instances of addslashes() used for SQL escaping with proper parameterized queries (prepared statements) or appropriate database-specific escaping functions like mysqli_real_escape_string or PDO::quote. Upgrade to a patched version of StatusNet/GNU Social if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StatusnetApplication
Affected:<= 2010

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm StatusNet installation
    Locate the StatusNet application directory and identify if your site uses StatusNet or its derivative (GNU Social) for microblogging functionality.
    Affected if StatusNet or an unmodified derivative is present on the system.
  2. Determine StatusNet version
    Check the version file or changelog in the StatusNet installation directory. Look for version information in a VERSION file, composer.json, or the main index.php entry point.
    Affected if The installed version is from 2010 or earlier (any version up to and including 2010 releases).
  3. Search for addslashes() in database code
    Grep the source code for 'addslashes' in PHP files that handle database operations, particularly files in the lib/ or include/ directories related to database abstraction, user data storage, or query construction.
    Affected if addslashes() is used for escaping values before inserting them into SQL queries.
  4. Verify character encoding configuration
    Check the database connection settings and configuration files for the character encoding (charset) being used. Look at config files like config.php or database schema definitions.
    Affected if The database uses a multi-byte character encoding (such as UTF-8) where addslashes() can fail to properly escape certain characters, allowing bypass.
  5. Identify user input paths
    Review PHP files that process user-submitted data (form inputs, API parameters, profile fields) and pass them to database queries without parameterized prepared statements.
    Affected if User-controllable data flows directly into SQL queries that rely on addslashes() for escaping.

You are affected if StatusNet version 2010 or earlier is running and the codebase contains addslashes() used for SQL escaping, especially when operating with multi-byte character encodings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2010
Interim mitigation

Replace all instances of addslashes() used for SQL escaping with proper parameterized queries (prepared statements) or appropriate database-specific escaping functions like mysqli_real_escape_string or PDO::quote. Upgrade to a patched version of StatusNet/GNU Social if available.

Recommended fix Moderate confidence

GNU Social (the maintained fork of the original open-source Statusnet)

  1. 1. Identify the current Statusnet installation version and verify it is <= 2010
  2. 2. Backup the entire Statusnet database and web root directory
  3. 3. Export all user data, posts, and configuration from the existing Statusnet instance
  4. 4. Install GNU Social (the maintained fork of Statusnet) on a new server or in a new directory
  5. 5. Import the backed-up data into the new GNU Social installation
  6. 6. Configure the web server to point to the new GNU Social installation
  7. 7. Verify all functionality works correctly after migration
  8. 8. Decommission the old Statusnet installation
Caveat GNU Social may have different plugin APIs and configuration options; some older plugins may require updates or replacement

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Statusnet Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4660 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data