CVE-2025-1270
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 · uneditedInsecure direct object reference (IDOR) vulnerability in Anapi Group's h6web, allows an authenticated attacker to access other users' information by making a POST request and modifying the “pkrelated” parameter in the “/h6web/ha_datos_hermano.php” endpoint to refer to another user. In addition, the first request could also allow the attacker to impersonate other users. As a result, all requests made after exploitation of the IDOR vulnerability will be executed with the privileges of the impersonated user.
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 confidenceIDOR vulnerability in h6web's /h6web/ha_datos_hermano.php endpoint allows authenticated attackers to access or modify other users' data by manipulating the pkrelated parameter in POST requests. The flaw enables full user impersonation, causing all subsequent requests to execute with the impersonated user's privileges.
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 dataall versionsCVSS 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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Anapi H6web installationSearch the system for the h6web application directory or check web server document roots for a folder named 'h6web' containing PHP filesAffected if The h6web application directory exists on the server
-
Verify vulnerable endpoint existsCheck for the presence of the file ha_datos_hermano.php within the /h6web/ directory. This is typically found at paths like /var/www/html/h6web/ha_datos_hermano.php or within the web application's document rootAffected if The file ha_datos_hermano.php exists in the h6web directory
-
Identify authentication mechanismReview the application's authentication system to determine how user sessions are managed. Check if the application uses session tokens, cookies, or API keys for authenticated accessAffected if The application uses an authentication mechanism that can be exploited for session hijacking
-
Test endpoint for broken object-level authorizationWith valid authentication credentials, submit a POST request to /h6web/ha_datos_hermano.php with the pkrelated parameter set to a value corresponding to a different user's data. Compare the response to verify if unauthorized data access or modification occursAffected if The endpoint returns data or performs actions for a pkrelated value that does not belong to the authenticated user, indicating IDOR vulnerability
-
Review access logs for suspicious parameter patternsExamine web server access logs (apache2, nginx) for POST requests to ha_datos_hermano.php where the pkrelated parameter contains unusual or sequential values that may indicate enumeration or impersonation attemptsAffected if Logs show POST requests to ha_datos_hermano.php with varying pkrelated parameter values from a single authenticated session
The environment is affected if Anapi H6web is installed and the ha_datos_hermano.php endpoint exists, as all versions of this product contain the IDOR vulnerability that allows unauthorized access via pkrelated parameter manipulation.
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 object-level authorization checks validating that the authenticated user has permission to access the requested resource identified by pkrelated before returning any data or executing actions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1270 — 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-1270 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