CVE-2025-28891
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 jazzigor price-calc price-calc allows Stored XSS.This issue affects price-calc: from n/a through <= 0.6.3.
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 confidenceCSRF vulnerability in price-calc plugin enables attackers to craft malicious requests that trick authenticated administrators into inadvertently injecting persistent malicious scripts (Stored XSS) into price calculation pages. The attack exploits the lack of anti-CSRF tokens on forms, allowing unauthorized state-changing actions that store XSS 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 if price-calc plugin is installedCheck your system for any installed plugin component named 'price-calc' or containing price calculation functionality. Review your plugin/component inventory or look for price calculation related files/modules in your web application.Affected if The price-calc plugin or component is present in your environment.
-
Locate the price calculation admin formsNavigate to the price-calc plugin administration interface and identify all forms used for creating or editing price calculations, pricing rules, or related configuration pages.Affected if You have access to admin forms in a price calculation plugin.
-
Inspect forms for anti-CSRF tokensView the HTML source of the price calculation admin forms and check whether each form includes a hidden anti-CSRF token field (typically named _token, csrf_token, nonce, or similar). Check if the form submission validates this token server-side.Affected if Forms lack anti-CSRF token fields or the tokens are not validated on submission.
-
Review stored price calculation pages for XSSAccess the price calculation pages as they would appear to end users (frontend). View the page source and check for any injected script tags, event handlers, or suspicious HTML in price display areas, calculation results, or configuration labels.Affected if Malicious scripts or unsanitized HTML/JavaScript are present in the rendered price calculation output.
-
Check admin action logs for suspicious requestsReview server and application logs for any unauthorized or unexpected POST/PUT requests to price calculation endpoints, particularly those originating from admin sessions that may have been tricked via CSRF.Affected if There are anomalous state-changing requests to price calculation endpoints in the logs.
You are affected if you have a price-calc plugin installed AND its admin forms lack anti-CSRF token protection AND stored XSS payloads are present in your price calculation pages.
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 on all state-changing forms and validate/sanitize all user inputs and outputs to prevent stored XSS. Users should update to a patched version when available or remove the plugin until fixed.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28891 — 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-28891 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