How severe is CVE-2021-22513?

CVE-2021-22513 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

How do I fix CVE-2021-22513?

Update org.jenkins-ci.plugins:hp-application-automation-tools-plugin to 7.2.3-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-22513 is resolved across your whole dependency graph.

How do I detect CVE-2021-22513 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:hp-application-automation-tools-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-22513 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2021-22513 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-22513 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-22513?

CVE-2021-22513 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-22513?

CVE-2021-22513 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-22513 published, and has it been updated?

CVE-2021-22513 was published on May 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2021-22513 — hp-application-automation…

MEDIUMFix: jenkinsci/hpe-application-automation-tools-plugin@497a143

CVE-2021-22513 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:hp-application-automation-tools-plugin. A fix is available for org.jenkins-ci.plugins:hp-application-automation-tools-plugin — see the affected versions and patch details below.

Missing permission checks in Micro Focus Application Automation Tools Plugin

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:hp-application-automation-tools-plugin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Micro Focus Application Automation Tools Plugin 6.7 and earlier does not perform permission checks in methods implementing form validation.

This allows attackers with Overall/Read permission to connect to attacker-specified URLs using attacker-specified username and password.

Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Micro Focus Application Automation Tools Plugin 6.8 requires POST requests and Overall/Administer permission for the affected form validation methods.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:hp-application-automation-tools-plugin`	all versions	7.2.3-beta`org.jenkins-ci.plugins:hp-application-automation-tools-plugin:7.2.3-beta`

Affected Products

1 product · 1 configurations

Application

application automation toolsmicrofocus

≤ 6.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:hp-application-automation-tools-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:hp-application-automation-tools-plugin to 7.2.3-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-22513 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Micro Focus Application Automation Tools Plugin 6.7 and earlier does not perform permission checks in methods implementing form validation. This allows attackers with Overall/Read permission to connect to attacker-specified URLs using attacker-specified username and password. Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. Micro Focus Application Automation Tools Plugin 6.8 requires POST requests and Overall/Administer permission for the affected form validation methods.

O3 Security · Impact-Aware SCA

Is CVE-2021-22513 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 24, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2021-22513

References

Advisorynvd.nist.gov · CVE 2021 22513 Webgithub.com · 497a143d9a95e9c937501ca329fe0dae22a0d9cd Webjenkins.io · 2021 04 07 Packagegithub.com · hpe application automation tools plugin

Related vulnerabilities

Also affects hp-application-automation-tools-plugin

This CVE is medium severity; 3 of 3 other CVEs affecting hp-application-automation-tools-plugin are rated as high or higher (top: high).

CVE-2021-22510CVE-2021-22512CVE-2021-22511

Same weakness: CWE-862

This CVE is medium severity; 5 of 5 other CVEs with CWE-862 are rated as high or higher (top: high).

CVE-2026-93363CVE-2026-116677CVE-2026-116794CVE-2026-118759GHSA-w9x9-j56r-h98rBrowse all CWE-862

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2021-22513 — hp-application-automation…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-22513 in your dependencies?