CVE-2026-53867: Capgo Profile Image Deletion Vulnerability
Capgo versions prior to 12.128.2 do not properly clean up user profile images from storage when those images are replaced or deleted. This means old image files remain accessible on the backend server even after users think they've removed them. An attacker with a user account can leverage previously shared or discovered image URLs to retrieve these orphaned files, potentially accessing private user photos or other sensitive image data that should have been deleted.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses (CWE)
- CWE-459
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-12 / 2026-07-14
NVD description (verbatim)
Capgo before 12.128.2 fails to delete previously uploaded profile images from backend storage when users replace or remove them. Attackers can access orphaned image files through previously generated URLs, allowing unauthorized retrieval of user-uploaded content.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53867 is an improper resource cleanup vulnerability (CWE-459) in Capgo's profile image handling. When users replace or remove profile pictures, the application fails to delete the corresponding files from backend storage, leaving them accessible via their original URLs. The vulnerability requires authenticated access (PR:L in CVSS) and results in low confidentiality impact through information disclosure. The attack has no prerequisite user interaction (UI:N) and operates over the network without complexity constraints (AV:N/AC:L).
Business impact
This vulnerability creates a data retention risk where user-uploaded personal images persist beyond their intended lifecycle. For organizations deploying Capgo, the primary concern is unintended information disclosure—users believe deleted images are removed, but those images remain recoverable. This affects user trust and may create compliance issues under data minimization requirements in privacy regulations like GDPR, CCPA, or similar frameworks that require data be deleted when no longer needed. The impact is contained to image data and requires authentication, limiting enterprise risk, but still represents a control gap in data handling.
Affected systems
All Capgo installations prior to version 12.128.2 are vulnerable. The issue affects any deployment where users upload profile images. No other vendors or products are listed as affected. Organizations running Capgo should verify their version number immediately.
Exploitability
Exploitation requires a valid user account on the target Capgo instance (PR:L). The attack surface is limited to image URLs previously shared or obtained—an attacker cannot enumerate all orphaned images without prior knowledge of URL patterns or specific file references. While the barrier to entry is moderate (needing credentials), the technical execution is straightforward: if an attacker has or discovers a URL to a deleted image, retrieval is trivial. The vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog, though this does not guarantee absence of real-world exploitation.
Remediation
Upgrade Capgo to version 12.128.2 or later. This release includes corrected image lifecycle management that removes files from backend storage when images are replaced or deleted. Organizations should apply this patch on a prioritized but not emergency timeline given the medium severity rating and authentication requirement. After patching, no additional manual cleanup of orphaned images is documented as necessary, though organizations may wish to audit historical storage for sensitive orphaned files.
Patch guidance
1. Verify current Capgo version in your deployment. 2. Review Capgo's official release notes for version 12.128.2 to confirm the fix is included. 3. Test the patch in a non-production environment to validate image deletion behavior. 4. Plan and execute the upgrade during a maintenance window if your deployment serves production users. 5. Confirm post-patch that deleted profile images are no longer accessible via previously known URLs. 6. Monitor Capgo's advisory channels for any related patches addressing similar cleanup issues.
Detection guidance
Identify potentially exposed images by reviewing access logs for requests to user profile image URLs where those users have subsequently deleted or replaced their images. Cross-reference image URLs in logs against current user profiles to detect orphaned file access. If possible, audit backend storage to enumerate image files and verify they correspond to active profile images. Security teams may also monitor for suspicious patterns of image URL enumeration or repeated access to images from accounts other than their owners, though authentication requirement limits this risk.
Why prioritize this
This vulnerability merits timely but not emergency remediation. The CVSS score of 4.3 (MEDIUM) reflects the limited scope: information disclosure only, requiring authentication, affecting only uploaded image data. However, it should be prioritized above low-severity items because it directly violates user expectations of data deletion and may have compliance implications. Organizations with strict data minimization obligations or those subject to regulatory audit should elevate priority. Schedule the patch within normal change windows—likely within 30–60 days depending on your risk tolerance and Capgo's role in your architecture.
Risk score, explained
The CVSS 3.1 score of 4.3 reflects a Medium severity: AV:N (network reachable) and AC:L (no special conditions) mean the vulnerability is easily accessed, but PR:L (authenticated access required) and C:L/I:N/A:N (low confidentiality impact only, no integrity or availability impact) constrain the overall score. The vulnerability does not escalate privileges, corrupt data, or degrade system availability—it only discloses previously uploaded images that should have been deleted. The score appropriately balances the ease of network exploitation against the narrowed scope and authentication barrier.
Frequently asked questions
Can an unauthenticated attacker exploit this vulnerability?
No. CVE-2026-53867 requires a valid user account on the Capgo instance (PR:L in the CVSS vector). An attacker must authenticate to the system, though they may be able to access orphaned images belonging to other users if they know or guess the image URLs.
Will upgrading to 12.128.2 delete orphaned images already on disk?
The vulnerability patch ensures that future image deletions are handled correctly. The vendor documentation does not explicitly state whether the upgrade automatically purges previously orphaned files from storage. Organizations concerned about historical sensitive images should consider manual auditing and cleanup of backend storage, particularly if images contain personally identifiable information.
What if we cannot upgrade immediately due to operational constraints?
Mitigate by restricting image URL sharing and monitoring for unauthorized access to image endpoints. Implement network-level controls to limit access to profile image storage URLs, and monitor logs for unusual image retrieval patterns. However, these are interim measures—plan to upgrade within your standard patch cycle (typically 30–60 days for medium-severity vulnerabilities).
Is this vulnerability exploited in the wild?
CVE-2026-53867 is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog. However, absence from the KEV list does not guarantee no active exploitation. Given the straightforward nature of the flaw, organizations should not rely on KEV status alone for prioritization decisions.
This analysis is provided for informational purposes and represents a point-in-time assessment based on available CVE data and vendor information as of the publication date. SEC.co does not provide legal or compliance advice. Organizations subject to regulatory requirements should consult with their compliance and legal teams regarding patch timelines and data retention obligations. Verify all patch version numbers and remediation steps against the official Capgo advisory before deployment. Organizations should conduct their own risk assessment based on their specific deployment, threat model, and business context. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-5038MEDIUMmulter Denial of Service via Orphaned Upload Files
- CVE-2016-20064MEDIUMWP Vault 0.8.6.6 Arbitrary File Read via Directory Traversal
- CVE-2016-20067MEDIUMWordPress CP Polls CSRF Vulnerability
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20074MEDIUMWordPress Lazy Content Slider CSRF Vulnerability – Patch & Detection Guide
- CVE-2016-20077MEDIUMWordPress Photocart Link Plugin Local File Inclusion Vulnerability
- CVE-2016-20078MEDIUMWordPress IMDb Profile Widget Local File Inclusion Vulnerability
- CVE-2016-20079MEDIUMWordPress Dharma Booking Local File Inclusion Vulnerability