CVE-2023-22271· NVD / CVE Program· CNA adobe

AEM Weak Cryptography for Passwords Security feature bypass

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.81% (FIRST EPSS); higher than 56% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Experience Manager versions 6.5.15.0 (and earlier) are affected by a Weak Cryptography for Passwords vulnerability that can lead to a security feature bypass. A low-privileged attacker can exploit this in order to decrypt a user's password. The attack complexity is high since a successful exploitation requires to already have in possession this encrypted secret.

MediumCVSS 5.3 · v3.1—No exploit No fix recorded

BDU:2023-01550

Published: Mar 22, 2023
Updated: Jun 17, 2026
EPSS: 0.8% · 56th percentile
CWE: CWE-261

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.3
CNA · adobe: 5.3; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
adobe	experience manager	cpe:2.3:a:adobe:experience_manager
adobe	experience manager cloud service	cpe:2.3:a:adobe:experience_manager_cloud_service

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

adobe experience managerbefore 6.5.16.0
adobe experience manager cloud servicebefore 2023.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

Adobe Experience Manager
- unspecified and later · up to and including 6.5.15.0affected
- unspecified and later · up to and including Noneaffected

Same product

adobe: all records

Other highest-scoring records for the same primary product.

CVE-2025-49533Adobe Experience Manager (MS) | Deserialization of Untrusted Data (CWE-502)
55Plan
CVE-2018-5006Adobe Experience Manager versions 6.4 and earlier have a Server-Side Request Forgery vulnerability.
46Plan
CVE-2019-7964Adobe Experience Manager versions 6.5, and 6.4 have an authentication bypass vulnerability.
42Plan
CVE-2017-3108Adobe Experience Manager 6.2 and earlier has a malicious file execution vulnerability.
42Plan
CVE-2019-8088Adobe Experience Manager versions 6.5, 6.4, 6.3 and 6.2 have a command injection vulnerability.
41Plan
CVE-2021-40722AEM Forms Improper Restriction of XML External Entity Reference
40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).