CVE-2026-72550 in Friendica's photo module is an unauthenticated SQL injection with critical severity, but the vulnerability's mechanism reveals a deeper architectural problem that changes how you should respond. The exploitation uses bare PDO::query() with direct string interpolation for a SHOW COLUMNS query—a pattern that cannot be fixed with prepared statements, since PDO cannot bind table names or column identifiers. This means the fix, whatever form it takes, won't be a simple parameterization; it requires identifier quoting or whitelisting, and every other dynamic column, table, or ORDER BY expression in this module is likely vulnerable to the same class of flaw. Audit your Friendica deployment for analogous PDO::query() calls with string interpolation across the entire photo module and related data access code. The stacked injection capability means attackers aren't limited to data exfiltration—they can modify or delete records, which on a federated platform means compromising a node gives them access to authentication tokens and cross-platform relationships that other systems trust. The 2026.08-dev branch designation is a red flag: if the fix only lands in a future release rather than patching stable versions, a significant portion of the fediverse footprint remains exploitable for months or years, and your node may be exposed through federated partners running unpatched instances. Treat this as a design boundary violation requiring architectural refactoring of your data access layer, not merely a one-line patch to apply and forget.
CVE-2026-72550
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 · uneditedAn SQL injection vulnerability in Friendica through the 2026.08-dev branch allows unauthenticated remote attackers to execute arbitrary SQL statements via the photo-view order parameter. The parameter is concatenated unescaped into a SHOW COLUMNS query via a bare PDO::query() call, enabling stacked statement injection. An unauthenticated attacker can read, modify, or delete the entire database.
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 analysisUser input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.
General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
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.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $5,750. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-72550 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-72550 in Friendica's photo module is an unauthenticated SQL injection with critical severity, but the vulnerability's mechanism reveals a deeper architectural problem that changes how you should respond. The exploitation uses bare PDO::query() with direct string interpolation for a SHOW COLUMNS query—a pattern that cannot be fixed with prepared statements, since PDO cannot bind table names or column identifiers. This means the fix, whatever form it takes, won't be a simple parameterization; it requires identifier quoting or whitelisting, and every other dynamic column, table, or ORDER BY expression in this module is likely vulnerable to the same class of flaw. Audit your Friendica deployment for analogous PDO::query() calls with string interpolation across the entire photo module and related data access code. The stacked injection capability means attackers aren't limited to data exfiltration—they can modify or delete records, which on a federated platform means compromising a node gives them access to authentication tokens and cross-platform relationships that other systems trust. The 2026.08-dev branch designation is a red flag: if the fix only lands in a future release rather than patching stable versions, a significant portion of the fediverse footprint remains exploitable for months or years, and your node may be exposed through federated partners running unpatched instances. Treat this as a design boundary violation requiring architectural refactoring of your data access layer, not merely a one-line patch to apply and forget.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-72550 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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