dbcve.org
SmangaApplication · Lkw199711

CVE-2025-70833

CRITICAL · 9.4 CVSS v3.1 Published 2026-02-20
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
An Authentication Bypass vulnerability in Smanga 3.2.7 allows an unauthenticated attacker to reset the password of any user (including the administrator) and fully takeover the account by manipulating POST parameters. The issue stems from insecure permission validation in check-power.php.

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

Smanga 3.2.7 contains an authentication bypass vulnerability in check-power.php where insecure permission validation allows unauthenticated attackers to manipulate POST parameters and reset passwords for any user account, including administrators, leading to complete account takeover.

MitigationImplement proper authentication and authorization checks in check-power.php to verify the requesting user's identity and permissions before processing password reset requests, and require valid session tokens or existing authentication for any account modification operations.

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
SmangaApplication
Affected:= 3.2.7

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify Smanga installation and version
    Locate the Smanga installation directory and check for version information. Common locations include a version file, about page, or manifest file. Alternatively, check the source code for version markers.
    Affected if The installed version is exactly 3.2.7 (note: only this specific version is affected)
  2. Verify check-power.php exists
    Search for the file check-power.php in the web application directory, typically under the main Smanga source folder or admin/includes directories.
    Affected if The file check-power.php exists in the Smanga installation directory
  3. Inspect password reset logic in check-power.php
    Open check-power.php and examine the code that handles password reset functionality. Look for POST parameter handling related to password modification and any permission/authorization validation (or lack thereof).
    Affected if The code processes password reset requests without proper authentication verification or uses insecure permission validation logic
  4. Check for unauthenticated access exposure
    Determine if the Smanga application is accessible over the network without authentication. Attempt to access check-power.php directly via HTTP/HTTPS without providing valid credentials.
    Affected if The vulnerable endpoint is reachable without authentication (the vulnerability allows unauthenticated attacks)
  5. Look for password reset parameter handling
    Review how POST parameters are handled in check-power.php. Specifically check if user account identifiers or password values are taken directly from POST input without validation.
    Affected if POST parameters controlling password reset are processed without validation, allowing manipulation of any user account

You are affected if Smanga version 3.2.7 is installed, check-power.php exists with the vulnerable password reset logic, and the endpoint is accessible without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks in check-power.php to verify the requesting user's identity and permissions before processing password reset requests, and require valid session tokens or existing authentication for any account modification operations.

Fix this in Smanga Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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