dbcve.org
Agilepoint NxApplication · Agilepoint

CVE-2022-30619

HIGH · 8.8 CVSS v3.1 Published 2022-07-06
Fix available
A fix is available. Upgrade to 8.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Editable SQL Queries behind Base64 encoding sending from the Client-Side to The Server-Side for a particular API used in legacy Work Center module. He attack is available for any authenticated user, in any kind of rule. under the function : /AgilePointServer/Extension/FetchUsingEncodedData in the parameter: EncodedData

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

SQL injection vulnerability in AgilePoint Server's /AgilePointServer/Extension/FetchUsingEncodedData API endpoint where SQL queries are base64-encoded client-side and decoded server-side. Any authenticated user can manipulate the EncodedData parameter to execute arbitrary SQL commands regardless of rule configuration.

MitigationReplace dynamic SQL construction with parameterized queries/prepared statements, implement strict input validation on decoded data, and enforce proper authorization checks regardless of user authentication status.

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
Agilepoint NxApplication
Affected:< 8.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 AgilePoint product and version
    Locate the installed AgilePoint Nx version number through the application UI (typically in Help > About) or check the installation directory for version metadata files
    Affected if Installed version is any version prior to 8.0 (versions < 8.0)
  2. Verify FetchUsingEncodedData endpoint exists
    Check if the API endpoint /AgilePointServer/Extension/FetchUsingEncodedData is present on the server by inspecting the deployed web application files or attempting a HEAD request to the endpoint
    Affected if The endpoint exists and is accessible in the deployed application
  3. Confirm user authentication is enabled
    Review the authentication configuration for the AgilePoint Server to verify that user authentication is active (check web.config or equivalent configuration for authentication settings)
    Affected if Authentication is enabled and users can log in to the application
  4. Check EncodedData parameter acceptance
    With an authenticated session, submit a test request to the FetchUsingEncodedData endpoint with a base64-encoded value in the EncodedData parameter and observe if the server processes and returns a response
    Affected if The endpoint accepts and processes the EncodedData parameter without rejecting it

The environment is affected if AgilePoint Nx version is below 8.0 AND the FetchUsingEncodedData endpoint is exposed to authenticated users who can supply base64-encoded SQL in the EncodedData parameter.

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 8.0 or later
Fixed in 8.0
Interim mitigation

Replace dynamic SQL construction with parameterized queries/prepared statements, implement strict input validation on decoded data, and enforce proper authorization checks regardless of user authentication status.

Recommended fix High confidence

AgilePoint Nx version 8.0 or later

  1. 1. Create a complete backup of the current AgilePoint Nx system including database and configuration files
  2. 2. Review AgilePoint Nx version 8.0 upgrade documentation and release notes for migration requirements
  3. 3. Upgrade AgilePoint Nx to version 8.0 or later
  4. 4. After upgrade, verify the /AgilePointServer/Extension/FetchUsingEncodedData endpoint no longer accepts injectable SQL via the EncodedData parameter
  5. 5. Test that the Work Center module functions correctly post-upgrade
Caveat Review release notes for potential breaking changes when upgrading from versions prior to 8.0

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

Fix this in Agilepoint Nx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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