dbcve.org
FeehicmsApplication · Feehi

CVE-2025-15264

HIGH · 7.3 CVSS v3.1 Published 2025-12-30
Fix available
A fix is available. Upgrade to after 2.1.1 or later.
See remediation →
82/100
Remediation priority · High
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
A vulnerability was determined in FeehiCMS up to 2.1.1. Impacted is an unknown function of the file frontend/web/timthumb.php of the component TimThumb. Executing manipulation of the argument src can lead to server-side request forgery. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in FeehiCMS up to v2.1.1 in the timthumb.php component. The src parameter in frontend/web/timthumb.php can be manipulated by attackers to force the server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services or facilitating further attacks.

MitigationRemove or disable the vulnerable timthumb.php file if not actively used, or apply any available vendor patch. If timthumb is required, implement strict allowlist validation for the src parameter and restrict outbound network access from the web server.

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
FeehicmsApplication
Affected:<= 2.1.1

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
Low
Integrity
Low
Availability
Low

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

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 FeehiCMS installation
    Check for FeehiCMS files in the web root directory, typically looking for common FeehiCMS directories such as frontend/, backend/, common/, or config files like config/db.php
    Affected if FeehiCMS is installed on the server
  2. Check FeehiCMS version
    Locate the version file or admin panel that displays the installed FeehiCMS version. Common locations include a VERSION file in the root, composer.json, or within the admin interface under system information
    Affected if Installed version is 2.1.1 or lower
  3. Locate timthumb.php component
    Verify the existence of frontend/web/timthumb.php file within the FeehiCMS installation directory
    Affected if The file frontend/web/timthumb.php exists in the web-accessible directory
  4. Test src parameter exposure
    Make a GET request to frontend/web/timthumb.php with a manipulated src parameter (for example: ?src=http://127.0.0.1) and observe if the server attempts the request
    Affected if The timthumb.php script processes the src parameter and makes outbound HTTP requests

A user is affected if FeehiCMS version 2.1.1 or lower is installed AND the timthumb.php file exists in frontend/web/ and is accessible, allowing the src parameter to be manipulated for SSRF attacks.

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 2.1.1
Interim mitigation

Remove or disable the vulnerable timthumb.php file if not actively used, or apply any available vendor patch. If timthumb is required, implement strict allowlist validation for the src parameter and restrict outbound network access from the web server.

Recommended fix Moderate confidence
  1. 1. Locate and identify the vulnerable file frontend/web/timthumb.php in the FeehiCMS installation
  2. 2. Remove or delete the timthumb.php file if it is not required for the application's functionality
  3. 3. If timthumb.php is required, implement access controls to prevent external users from accessing the script via web requests
  4. 4. Configure web server (Apache/Nginx) to deny access to the timthumb.php file for external visitors
  5. 5. Alternatively, replace TimThumb functionality with a secure alternative image processing library
  6. 6. Review all other TimThumb instances across the application for similar SSRF vulnerabilities
  7. 7. Implement web application firewall (WAF) rules to detect and block SSRF attempts targeting the src parameter
Caveat No official fix available from vendor; removing timthumb.php may break image resizing functionality if used by the application

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

Fix this in Feehicms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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