CVE-2025-53709
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 · uneditedSecure-upload is a data submission service that validates single-use tokens when accepting submissions to channels. The service only installed on a small number of environments. Under specific circumstances, privileged users of secure-upload could have selected email templates not necessarily created for their enrollment when sending data upload requests. Authenticated and privileged users of one enrollment could have abused an endpoint to redirect existing submission channels to a dataset they control. An endpoint handling domain validation allowed unauthenticated users to enumerate existing enrollments. Finally, other endpoints allowed enumerating if a resource with a known RID exists across enrollments. The affected service has been patched with version 0.815.0 and automatically deployed to all Apollo-managed Foundry instances.
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 confidenceSecure-upload service in Foundry had multiple authorization flaws: privileged users could access email templates outside their enrollment, authenticated users could redirect submission channels to attacker-controlled datasets, and endpoints allowed unauthenticated enumeration of enrollments and resources via predictable RIDs.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Foundry versionLocate the Foundry version file or check the admin dashboard for the current deployed version. Common locations: version file in installation directory, or admin panel > System > About.Affected if Version is below v0.815.0 (the patched release)
-
Verify secure-upload service is enabledCheck Foundry configuration files or admin settings to confirm the secure-upload module/service is active. Look for secure_upload or upload_service settings in config files or database.Affected if Secure-upload service is enabled and running
-
Inspect email template access controlsAs a privileged user (with enrollment access), attempt to access email templates from an enrollment you are NOT enrolled in. Check if the API or UI allows retrieval of templates outside your enrollment scope.Affected if Templates from other enrollments are accessible to privileged users outside their enrollment
-
Review submission channel configurationExamine submission channel settings in the secure-upload service. Check if the channel destination can be configured to point to external URLs or custom dataset endpoints. Look for destination_url, redirect, or dataset_link fields.Affected if Submission channels can be redirected to user-controlled external endpoints
-
Check for predictable RID enumerationAnalyze API endpoint behavior for enrollment or resource IDs. Send sequential requests with incrementing RID values (e.g., /api/enrollments/1, /api/enrollments/2) without authentication to observe if data is returned.Affected if Unauthenticated requests with sequential IDs return enrollment or resource data
You are affected if running Foundry version below v0.815.0 with the secure-upload service enabled, and any of the authorization flaws (template access, channel redirection, RID enumeration) are present in your environment.
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.
dbcve · scopedFor Apollo-managed instances, the patch (v0.815.0) has been auto-deployed. Self-hosted deployments require manual upgrade. Organizations should verify the deployed version and audit access logs for signs of exploitation.
secure-upload version 0.815.0
- 1. Identify whether your Foundry instance is Apollo-managed or self-hosted/independently managed.
- 2. For Apollo-managed instances: No action required as the patch (version 0.815.0) has been automatically deployed.
- 3. For self-hosted/independently managed instances: Upgrade the secure-upload service to version 0.815.0 or later.
- 4. Verify the upgrade by checking the secure-upload service version after deployment.
- 5. Confirm that the authorization checks now properly enforce enrollment boundaries for email templates, submission channel redirects, domain validation, and RID enumeration.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53709 — 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-2025-53709 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