CVE-2026-50872
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 issue in the loopback request handling component of fossar selfoss v2.20-SNAPSHOT allows attackers to execute arbitrary commands and obtain sensitive information via supplying a crafted HTTP request.
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 confidencefossar selfoss v2.20-SNAPSHOT contains a command injection vulnerability in its loopback request handling component. Attackers can send crafted HTTP requests to execute arbitrary OS commands and read sensitive files. The loopback interface handling appears to insufficiently sanitize user input before passing it to system call functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm selfoss installationIdentify if the fossar selfoss application is installed on the system by checking for its web directory, configuration files, or running processesAffected if selfoss is installed and running
-
Check selfoss versionLocate the version file or check the selfoss codebase for the version identifier, typically found in a version.php, package.json, or similar metadata file within the selfoss installation directoryAffected if the installed version is 2.20-SNAPSHOT or any version prior to the patched release
-
Identify loopback request handling componentLocate the source code file responsible for loopback request handling within the selfoss installation, typically in the src/ or htdocs/ directory, and examine its request processing logicAffected if the loopback request handling component exists and is present in the installation
-
Verify network exposureCheck the web server configuration or firewall rules to determine if the selfoss application is accessible over the network from untrusted sourcesAffected if the application is exposed to network access without proper restriction
-
Inspect request handling codeExamine the loopback request handling code for lack of input sanitization or validation on HTTP request parameters that could be leveraged for command injectionAffected if the code does not sanitize or validate user-supplied input in request parameters
A user is affected if selfoss version 2.20-SNAPSHOT is running and the loopback request handling component is accessible without input validation safeguards.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a stable release beyond v2.20-SNAPSHOT that patches this vulnerability; if patching is not immediately possible, restrict access to loopback request endpoints via network-level controls or web server configuration.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50872 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50872 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
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.
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