dbcve.org
FluxcpApplication · Rathena

CVE-2024-45799

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-16
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
FluxCP is a web-based Control Panel for rAthena servers written in PHP. A javascript injection is possible via venders/buyers list pages and shop names, that are currently not sanitized. This allows executing arbitrary javascript code on the user's browser just by visiting the shop pages. As a result all logged in to fluxcp users can have their session info stolen. This issue has been addressed in release version 1.3. All users are advised to upgrade. There are no known workarounds for this vulnerability.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in FluxCP allows injection of arbitrary JavaScript via unsanitized vendor/buyer list pages and shop names, enabling session theft from all logged-in users.

MitigationUpgrade to FluxCP version 1.3 which implements proper input sanitization; no workarounds available.

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
FluxcpApplication
Affected:< 1.3.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify FluxCP installation
    Locate FluxCP installation directory. Common paths include /var/www/fluxcp, /home/user/public_html/fluxcp, or check web server document root for 'fluxcp' folder. Look for file 'includes/functions.php' or 'config.php' to confirm installation.
    Affected if FluxCP is present on the server and accessible via web
  2. Determine FluxCP version
    Open the FluxCP root directory and check for a VERSION file, or look in config.php for a version constant. Alternatively, check the git tags if using source control: git tag | tail -1
    Affected if Version is below 1.3.0 (e.g., 1.2.x or unversioned)
  3. Verify vendor/buyer list feature is accessible
    Check if the vendor/buyer list module is enabled. Examine config/server.php or config/modules.php for the 'vendor' or 'buyer' module configuration. Try accessing /?module=vendor or /?module=buyer via HTTP to confirm the feature is active.
    Affected if Vendor/buyer module is enabled and accessible to users
  4. Inspect stored shop names for unsanitized input
    Examine the database table for shop/vendor entries. Query: SELECT id, shop_name, owner FROM vendors WHERE shop_name LIKE '%<script%' OR shop_name LIKE '%onerror=%' OR shop_name LIKE '%onload=%'. Alternatively, view the vendor list page source in a browser and search for unescaped HTML characters.
    Affected if Database contains shop names with unescaped HTML/script tags, or rendered page shows raw HTML in shop name fields

User is affected if FluxCP version is below 1.3.0 AND the vendor/buyer list feature is enabled AND unsanitized shop/vendor names are present in the database or rendered.

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.

dbcve · scoped
Upgrade available Upgrade to 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Upgrade to FluxCP version 1.3 which implements proper input sanitization; no workarounds available.

Recommended fix High confidence

1.3.0

  1. Back up your current FluxCP installation and database
  2. Download FluxCP version 1.3.0 from the official repository (e.g., github.com/rathena/fluxcp)
  3. Replace existing FluxCP files with the new version 1.3.0
  4. Verify the application functions correctly after the upgrade
  5. Confirm the XSS vulnerability is fixed by testing that shop names and vendor/buyer list entries are properly sanitized and no longer execute injected JavaScript

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fluxcp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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