CVE-2025-23982
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 · uneditedMissing Authorization vulnerability in Gopi krishnan Fare Calculator fare-calculator allows Stored XSS.This issue affects Fare Calculator: from n/a through <= 1.1.
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 · high confidenceA missing authorization vulnerability in the Fare Calculator plugin allows authenticated users to inject malicious scripts via input fields that are stored and executed when other users view the data. This is a Stored XSS vulnerability stemming from insufficient authorization checks combined with lack of input sanitization.
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 Fare Calculator plugin is installedCheck your CMS/plugin directory for a Fare Calculator plugin or check the installed plugins list in your admin panelAffected if The Fare Calculator plugin is present in the system
-
Determine the installed version of the Fare Calculator pluginAccess the plugin settings or version information page in your admin panel, or inspect the plugin metadata file (typically version.txt, plugin.json, or the main plugin PHP file header)Affected if The installed version is unknown or falls within a vulnerable version range for this CVE
-
Inspect stored fare calculation data for malicious scriptsAccess the database tables that store fare calculation inputs (such as fare_records, calculations, or similar data tables) and examine stored values in input fields (origin, destination, passenger count, etc.) for unsanitized HTML/script tagsAffected if Stored data contains unescaped HTML tags, script elements, or event handler attributes in any fare input fields
-
Verify authorization controls on fare calculation endpointsTest creating fare calculations as a low-privileged authenticated user, then attempt to view or edit those calculations as a different user or admin role to verify if proper access controls existAffected if Users can inject or view data from other users without proper authorization checks
-
Test input fields for XSS vulnerabilitySubmit a benign XSS test payload (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) into fare calculator input fields, then view the stored data as a different user or admin to see if the script executesAffected if The submitted script payload executes when viewed by another user, confirming stored XSS
The environment is affected if the Fare Calculator plugin is installed and either the version is vulnerable or stored XSS payloads can be executed by viewing fare calculation data as a different user.
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 authorization checks on all fare calculation input endpoints and apply output encoding/sanitization to prevent script execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23982 — 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-23982 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