dbcve.org
ArcherApplication · Rsa

CVE-2022-26948

HIGH · 7.5 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to 6.9.1.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The Archer RSS feed integration for Archer 6.x through 6.9 SP1 (6.9.1.0) is affected by an insecure credential storage vulnerability. A malicious attacker may obtain access to credential information to use it in further attacks.

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

The Archer RSS feed integration for versions 6.x through 6.9 SP1 stores credentials insecurely, allowing a malicious attacker to potentially retrieve stored credential information. This insecure storage exposes sensitive authentication data that could be leveraged for further attacks against the platform or related systems.

MitigationUpgrade to Archer 6.9 SP2 or later which addresses the insecure credential storage vulnerability. If immediate patching is not possible, review and rotate any credentials used in RSS feed integrations and monitor for unauthorized access.

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
ArcherApplication
Affected:>= 6.1.0.0, < 6.9.1.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Archer version
    Locate the Archer version number in the system via the About section in the Archer UI, or query the Archer instance metadata. Common locations include the Help > About menu in the web interface, or the installation/configuration documentation for version lookup methods.
    Affected if The installed version is 6.1.0.0 through 6.9.1.0 (any version >= 6.1.0.0 but < 6.9.1.1)
  2. Confirm RSS feed integration is configured
    Navigate to the Archer administration settings and review the list of active integrations. Specifically look for RSS feed-related integrations under Data Feed, Feed Sources, or Integration settings depending on your Archer UI structure. Query the Archer database for records in tables related to RSS or feed configurations.
    Affected if RSS feed integration is enabled and has been configured with one or more RSS feed sources
  3. Locate stored credentials for RSS feeds
    Inspect the Archer configuration database or configuration files where feed credentials are stored. Look for any entries containing username, password, API key, or authentication token fields associated with RSS feed definitions. Check both encrypted and allegedly encrypted storage locations.
    Affected if Credentials are present in any storage location associated with RSS feed configurations, regardless of whether they appear encrypted
  4. Verify credential storage mechanism
    Examine how the RSS feed credentials are persisted in the system. Review database tables or configuration files that store feed authentication data. Determine if credentials are stored in plain text, weakly encoded, or in reversible encryption rather than proper secure storage.
    Affected if Credentials are stored using weak, reversible, or non-encrypted methods rather than proper secure credential storage

You are affected if your Archer version falls between 6.1.0.0 and 6.9.1.0 and you have RSS feed integrations configured with stored credentials using insecure storage.

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

Upgrade to Archer 6.9 SP2 or later which addresses the insecure credential storage vulnerability. If immediate patching is not possible, review and rotate any credentials used in RSS feed integrations and monitor for unauthorized access.

Recommended fix Moderate confidence

6.9.1.1 or later

  1. Verify current Archer version by accessing the Administration > System Settings > About Archer page
  2. Review Archer 6.9.1.1 release notes for any prerequisites or special upgrade instructions
  3. Create a full backup of the Archer database and configuration files
  4. Test the upgrade in a non-production environment before deploying to production
  5. Apply the upgrade to production during a planned maintenance window following standard Archer upgrade procedures
  6. Verify the RSS feed integration functions correctly after upgrade
  7. Confirm credential storage has been addressed by reviewing system security settings
Caveat Standard Archer minor version upgrade considerations apply - review release notes for any configuration or integration changes

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

Fix this in Archer 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-26948 — 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-26948 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