dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-44028

HIGH · 7.1 CVSS v3.1 Published 2024-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in nicejob NiceJob nicejob allows Stored XSS.This issue affects NiceJob: from n/a through < 3.6.5.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in NiceJob allows authenticated attackers to inject malicious scripts through Stored XSS by tricking users into submitting crafted requests. The flaw exists in versions prior to 3.6.5, where the application lacks proper anti-CSRF tokens and input sanitization, enabling persistent script execution.

MitigationUpdate NiceJob to version 3.6.5 or later which contains the security fix. Additionally, implement anti-CSRF tokens on all state-changing forms and ensure proper output encoding to prevent XSS.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NiceJob version
    Locate the installed NiceJob version number in the application admin panel under 'About', 'Settings', or system information page. Alternatively, check the application source files, build metadata, or API endpoint response headers for version metadata.
    Affected if The installed version is lower than 3.6.5 (e.g., 3.6.4, 3.6.0, any version prior to 3.6.5).
  2. Verify anti-CSRF token presence
    Inspect the HTML source code of state-changing forms (submission forms, user profile updates, settings changes) by viewing page source or using browser developer tools. Look for hidden input fields containing tokens named 'csrf', 'token', 'xsrf', or similar, or check request headers for anti-CSRF tokens.
    Affected if Forms lack anti-CSRF token fields or tokens are not validated server-side on form submission.
  3. Test CSRF vulnerability
    Create a test HTML page with a form that auto-submits to the target NiceJob endpoint without a token. Send the crafted request while logged in as a test user and verify whether the action completes successfully without rejection.
    Affected if The action executes successfully without returning a 403 error or requiring a valid anti-CSRF token.
  4. Check for stored XSS injection points
    Review application forms that accept user input and display it back to other users (reviews, comments, profiles, messages). Submit a test script payload like <script>alert('test')</script> in input fields and check if it executes when viewed.
    Affected if User-supplied input is rendered without sanitization or encoding, allowing stored script execution.
  5. Inspect server-side input validation
    Review application logs, security scans, or intercept server responses to confirm whether input sanitization and output encoding are applied to user-generated content stored in the database.
    Affected if Stored content is not sanitized before saving or encoded before display to users.

You are affected if your NiceJob installation version is below 3.6.5 AND your forms lack anti-CSRF protection, allowing attackers to craft malicious requests that result in stored XSS execution.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update NiceJob to version 3.6.5 or later which contains the security fix. Additionally, implement anti-CSRF tokens on all state-changing forms and ensure proper output encoding to prevent XSS.

Recommended fix Moderate confidence

NiceJob version 3.6.5 or later

  1. 1. Backup your current NiceJob installation and database before proceeding with any upgrade.
  2. 2. Identify your current NiceJob version by accessing the admin panel or checking the application settings.
  3. 3. Download NiceJob version 3.6.5 or the latest stable release from the official NiceJob vendor repository or control panel.
  4. 4. Follow the vendor's documented upgrade procedure to apply the update.
  5. 5. After upgrading, verify the application is functioning correctly and test that the CSRF protection is working as expected.
  6. 6. Confirm the new version number reflects 3.6.5 or later in the admin interface.
Caveat No specific breaking changes documented in the CVE; standard upgrade precautions apply (backup before upgrading)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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