CVE-2025-25128
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 Request Forgery (CSRF) vulnerability in orlandolac Facilita Form Tracker facilita-form-tracker allows Stored XSS.This issue affects Facilita Form Tracker: from n/a through <= 1.0.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in Facilita Form Tracker allows attackers to inject malicious scripts through forged requests, resulting in Stored XSS. The lack of CSRF protection enables authenticated users to be tricked into submitting unintended form data containing malicious payloads.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Facilita Form Tracker installationSearch the system for Facilita Form Tracker files, directories, or services. Check web server configurations (Apache/Nginx/IIS) for applications named 'Facilita Form Tracker' or 'Facilita' and look for associated application directories.Affected if Facilita Form Tracker is present in the environment
-
Check installed versionLocate version information in the application's about page, configuration files, or metadata files (e.g., version.txt, manifest.json, or database version tables). Compare against any known version ranges provided by the vendor.Affected if The installed version lacks CSRF protection mechanisms or is older than patched releases
-
Inspect form HTML for CSRF tokensAccess forms within Facilita Form Tracker (create/edit form pages, submission endpoints). View the page source or intercept responses to examine if <input type='hidden' name='csrf'>, '_token', or similar anti-CSRF token fields are present in form markup.Affected if Forms lack CSRF token fields or anti-CSRF token validation logic in the HTML
-
Test form submission without tokenSubmit a form using a tool like curl or Burp Suite Repeater without including any CSRF token parameter. Observe whether the submission is accepted and processed successfully.Affected if Form submissions succeed without requiring a valid CSRF token
-
Verify input sanitization on stored dataSubmit a test payload like <script>alert(1)</script> through a form field. Retrieve and display the stored data (view the submitted form entry, report, or export) to see if the payload is rendered as raw HTML or executed.Affected if The malicious script is rendered/executed when viewing stored form data, indicating stored XSS is possible
The environment is affected if Facilita Form Tracker is present, forms accept submissions without CSRF tokens, and stored data renders unsanitized HTML/JavaScript.
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 anti-CSRF tokens for all form submissions and validate/sanitize all user inputs on the server side to prevent XSS injection.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25128 — 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-25128 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