CVE-2025-55341
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 · uneditedCross Site Scripting vulnerability in Quipux 4.0.1 through e1774ac allows anexos/anexos_nuevo.php asocImgRad.
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 confidenceCross-Site Scripting (XSS) vulnerability in Quipux 4.0.1 allows attackers to inject malicious scripts via the asocImgRad parameter in anexos/anexos_nuevo.php. The parameter lacks proper input sanitization or output encoding, enabling reflected XSS attacks.
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= 4.0.1CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Quipux versionLocate the Quipux installation directory and check version.php, version.txt, or the admin interface for the installed version number. Common paths include /var/www/html/quipux, /opt/quipux, or the application's root directory.Affected if The installed version is 4.0.1 exactly (the only affected version listed)
-
Locate the affected script fileNavigate to the web root and search for anexos/anexos_nuevo.php. This file handles file attachments and processes the asocImgRad parameter.Affected if The file anexos/anexos_nuevo.php exists in the Quipux web directory
-
Verify asocImgRad parameter handlingExamine the anexos/anexos_nuevo.php source code and search for occurrences of 'asocImgRad'. Check whether this parameter is used in any output (echo, print, or HTML rendering) without sanitization functions such as htmlspecialchars() or input validation.Affected if The asocImgRad parameter is processed and echoed back to the user without encoding or validation
-
Test for reflected XSSIf you have access to the application, send a crafted request to anexos/anexos_nuevo.php with a test payload in the asocImgRad parameter, such as asocImgRad=<script>alert(1)</script>, and verify whether the script executes in the response.Affected if The malicious script payload is reflected unescaped in the HTTP response
-
Check web server access logsReview web server access logs (Apache, Nginx, or IIS) for requests to anexos/anexos_nuevo.php containing unusual patterns in the asocImgRad parameter that may indicate exploitation attempts.
A user is affected if they are running Quipux version 4.0.1 and the anexos/anexos_nuevo.php file processes the asocImgRad parameter without sanitization.
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 input validation and output encoding for the asocImgRad parameter in anexos_nuevo.php, or upgrade to a patched version of Quipux if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55341 — 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-55341 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