CVE-2026-7165
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 · uneditedThe vulnerability is present in the ‘/addJugador’ endpoint: * The 'keyJugador' and 'keyJugadorObjectiu' parameters allow the modification of other users’ information without requiring prior authorization validation. This could enable an authenticated attacker to alter any user’s ID and change their information. * The ‘punts’ and ‘numObjectiusEliminats’ fields allow arbitrary data to be added because user input is not properly validated. This makes it possible to obtain authentic prizes, awarded by city councils, by falsifying game scores. * In the ‘tokens’ field, administrative privileges can be self-assigned without server validation or prior authentication. This vulnerability could allow an authenticated attacker to grant themselves administrator permissions and thus escalate privileges. * Numeric fields allow the entry of extremely long values, which can cause the system to crash. Successful exploitation of this vulnerability could allow an authenticated attacker to launch a denial-of-service (DoS) attack, preventing created games from being playable. * The ‘urlImatge’ parameter allows server-side requests to arbitrary URLs, enabling the retrieval of users’ internal IP addresses, access to internal services, reading of local files, and unauthorized interaction with third-party APIs. An authenticated attacker could gain access to sensitive data.
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 confidenceThis CVE describes multiple critical vulnerabilities in the '/addJugador' endpoint of an application, including IDOR via 'keyJugador' and 'keyJugadorObjectiu' parameters allowing unauthorized user data modification, improper input validation on 'punts' and 'numObjectiusEliminats' fields enabling score falsification for prize fraud, privilege escalation via self-assigned 'tokens' field, DoS via excessively long numeric values, and SSRF via the 'urlImatge' parameter enabling internal network reconnaissance and file access.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the /addJugador endpoint is exposedScan your application for the existence of the /addJugador endpoint using web vulnerability scanning tools or by reviewing your application route definitions and API documentation.Affected if The endpoint exists and is accessible to users without proper authorization controls.
-
Verify authorization controls on keyJugador and keyJugadorObjectiu parametersAttempt to submit requests to /addJugador with keyJugador or keyJugadorObjectiu values referencing other users' IDs while logged in as a different user. Compare the response and check if unauthorized data modification occurs.Affected if Requests with keyJugador/keyJugadorObjectiu pointing to other users succeed without proper ownership verification.
-
Detect score manipulation vulnerability on punts and numObjectiusEliminatsSubmit requests to /addJugador with arbitrary numeric values in the 'punts' and 'numObjectiusEliminats' fields (e.g., extremely high values or negative numbers) and verify if the application accepts them without validation.Affected if The application accepts arbitrary numeric values in these fields without strict type checking, range validation, or server-side verification.
-
Check for privilege escalation via tokens parameterReview the /addJugador endpoint's parameter schema and submit a request including a 'tokens' field with an elevated value, then verify if the user-assigned tokens are applied without admin verification.Affected if The application processes and honors a user-supplied 'tokens' parameter without validating it against the user's actual permissions.
-
Detect SSRF vulnerability via urlImatge parameterSubmit requests to /addJugador with internal IP addresses (e.g., 127.0.0.1, 192.168.x.x) or internal URLs in the 'urlImatge' parameter and observe if the application attempts to fetch or process them.Affected if The application makes outbound requests to user-supplied URLs in the urlImatge parameter without allowlist validation.
-
Check for DoS via oversized numeric inputsSubmit requests to /addJugador with extremely long numeric values (e.g., 999999999999999999999999) in numeric fields and observe application behavior and response times.Affected if The application accepts excessively long numeric values without length constraints, leading to performance degradation or crashes.
A user is affected if the /addJugador endpoint is exposed and lacks proper authorization checks, input validation, and URL allowlisting for the keyJugador, punts, tokens, and urlImatge parameters.
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 dataRemediate by implementing proper authorization checks for all user-modifiable parameters, validating and sanitizing all user inputs with strict type/length constraints, implementing allowlist-based URL validation for the urlImatge field, and adding rate limiting to prevent DoS.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7165 — 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-2026-7165 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