dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-25864

CRITICAL · 9.1 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Server Side Request Forgery (SSRF) vulnerability in Friendica versions after v.2023.12, allows a remote attacker to execute arbitrary code and obtain sensitive information via the fpostit.php component.

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

Server-Side Request Forgery (SSRF) vulnerability in Friendica's fpostit.php component affecting versions after v.2023.12. The flaw allows remote attackers to manipulate the server into making arbitrary HTTP requests to internal or external resources, potentially enabling code execution and exfiltration of sensitive information from internal network services.

MitigationRestrict network access from the application server and disable or restrict the fpostit.php component until an official patch is applied. Implement strict allowlist-based URL validation for any user-controlled URL parameters.

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
None

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

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. Identify Friendica installation
    Locate the Friendica installation directory on the server and check for the presence of the fpostit.php file within the include, src, or addon directories.
    Affected if The fpostit.php file exists in the Friendica installation directory.
  2. Determine Friendica version
    Check the version.php file in the Friendica root directory, the config/local.config.php file, or the admin panel to identify the installed Friendica version number.
    Affected if The installed version is newer than v.2023.12 (for example, v.2024.01, v.2024.02, or later).
  3. Verify fpostit functionality is accessible
    Attempt to access the fpostit.php endpoint directly via HTTP request (for example, https://your-server/fpostit.php) or check if the addon/module is loaded in the Friendica addon or module configuration.
    Affected if The fpostit.php component is enabled or accessible via web request and responds to requests.
  4. Inspect URL parameter handling
    Review the fpostit.php source code to identify if user-controlled URL parameters are processed without strict validation, specifically looking for curl or file_get_contents operations handling external URLs.
    Affected if The code contains logic to fetch URLs based on user input without allowlist-based validation.

You are affected if your Friendica installation is version v.2023.12 or earlier AND the fpostit.php component exists and is accessible, or if your version is newer than v.2023.12 with fpostit enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access from the application server and disable or restrict the fpostit.php component until an official patch is applied. Implement strict allowlist-based URL validation for any user-controlled URL parameters.

Recommended fix Moderate confidence

latest stable Friendica release (check github.com/friendica/friendica releases for current version)

  1. Check your current Friendica installation version by examining the version file or admin panel
  2. Identify if your version is after v.2023.12 (any version v.2024.01 or later)
  3. Backup your Friendica database and files before performing any upgrade
  4. Download the latest stable Friendica release from the official repository at github.com/friendica/friendica
  5. Replace your existing installation files with the new release files, preserving your configuration and addons
  6. Verify the fpostit.php component has been updated in the new release
  7. Test that the application functions normally after the upgrade
Caveat Review release notes for any breaking changes between your version and the latest release; backup before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25864 — 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-2024-25864 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