dbcve.org
WakymaApplication

CVE-2026-3024

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Stored Cross-Site Scripting (XSS) vulnerability in the Wakyma web application, specifically in the endpoint 'vets.wakyma.com/configuracion/agenda/modelo-formulario-evento'. A user with permission to create personalized accounts could exploit this vulnerability simply by creating a malicious survey that would harm the entire veterinary team. At the same time, a user with low privileges could exploit this vulnerability to access unauthorized data and perform actions with elevated privileges.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in Wakyma web application allows authenticated users with account creation permissions to inject malicious JavaScript via survey fields at the modelo-formulario-evento endpoint. The payload persists and executes when other users (including those with low privileges) access the crafted survey, enabling session hijacking, unauthorized data access, and privilege escalation attacks.

MitigationImplement output encoding and input validation/sanitization at the vulnerable endpoint and across all user-generated content fields to prevent script injection. Apply Content Security Policy headers and validate user permissions for survey creation to restrict abuse.

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
WakymaApplication
Affected:all versions

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Wakyma application is deployed
    Identify if the Wakyma web application is running in your environment by reviewing web server logs, installed applications, or checking for the application at its expected URL base path.
    Affected if Wakyma is actively running and accessible on your network or infrastructure.
  2. Locate the vulnerable endpoint
    Check if the modelo-formulario-evento endpoint exists and is accessible by attempting to access it at its expected path within your Wakyma installation (typically /modelo-formulario-evento or similar path under the Wakyma base URL).
    Affected if The modelo-formulario-evento endpoint responds to requests, indicating the vulnerable survey functionality is present.
  3. Verify authenticated access exists
    Review user accounts and permissions in your Wakyma system to determine if any user accounts have account creation permissions, which is required to exploit this vulnerability.
    Affected if There exists at least one authenticated user with account creation or elevated permissions in the Wakyma system.
  4. Identify survey creation capability
    Examine if the survey creation or form building feature is available to authenticated users with elevated permissions by reviewing user role configurations and permission tables in the application database or admin panel.
    Affected if Authenticated users with elevated permissions can create or modify surveys and forms.
  5. Check for existing injected content
    Inspect survey records and form data stored in the application database, specifically tables related to surveys or events, for any suspicious script tags, HTML, or JavaScript code that may indicate prior exploitation.
    Affected if Survey or event data contains unsanitized user input with script execution potential (script tags, event handlers, javascript: URIs).

Your environment is affected if Wakyma is running, the modelo-formulario-evento endpoint is accessible, and authenticated users with elevated permissions can create or modify surveys, as all versions of Wakyma are vulnerable to stored XSS at this endpoint.

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 output encoding and input validation/sanitization at the vulnerable endpoint and across all user-generated content fields to prevent script injection. Apply Content Security Policy headers and validate user permissions for survey creation to restrict abuse.

Fix this in Wakyma Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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