CVE-2025-62086
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 · uneditedMissing Authorization vulnerability in akazanstev Яндекс Доставка (Boxberry) boxberry allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Яндекс Доставка (Boxberry): from n/a through <= 2.34.
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 confidenceMissing authorization vulnerability in the Яндекс Доставка (Boxberry) integration allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to and including 2.34, where proper authorization checks are not enforced, potentially allowing unauthorized access to delivery-related functionality.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Яндекс Доставка (Boxberry) integration is installedReview your system's installed modules or plugins list to confirm the Yandex Delivery Boxberry integration component is present and enabledAffected if The integration module is found and active in the system
-
Determine the installed version of the Boxberry integrationLocate the version information for the Яндекс Доставка (Boxberry) integration module in your system (check module metadata, composer.json, or admin panel) and compare it against the affected range: versions up to and including 2.34Affected if The installed version is 2.34 or lower
-
Verify authorization is enforced on delivery endpointsTest the Boxberry integration API endpoints or review the endpoint configuration to confirm that authorization checks are properly executed before allowing access to delivery-related functionalityAffected if Authorization checks are missing or can be bypassed, allowing unauthenticated or unauthorized access
-
Inspect access control security level configurationExamine the security level settings for the Boxberry integration in the system configuration or admin panel to determine if access control is configured with reduced or incorrect privilegesAffected if The access control security level is set to a permissive or misconfigured state that does not enforce proper authorization
You are affected if the Яндекс Доставка Boxberry integration is installed with version 2.34 or lower AND authorization is not properly enforced or access control security levels are misconfigured.
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 dataImplement proper authorization checks across all endpoints and ensure access control security levels are correctly configured according to the principle of least privilege.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62086 — 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-62086 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