How severe is CVE-2007-2353?

CVE-2007-2353 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2007-2353?

CVE-2007-2353 affects the following packages: org.apache.axis:axis (Maven). Ecosystems affected: Maven.

How do I fix CVE-2007-2353?

Update org.apache.axis:axis to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-2353 is resolved across your whole dependency graph.

How do I detect CVE-2007-2353 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.axis:axis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2007-2353 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2007-2353, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2007-2353?

CVE-2007-2353 has an EPSS (Exploit Prediction Scoring System) score of 27.7%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2007-2353?

CVE-2007-2353 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2007-2353 published, and has it been updated?

CVE-2007-2353 was published on April 30, 2007 and was last updated on March 20, 2026. 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-2007-2353 — axis

MEDIUMFix: albfernandez/axis1-java@32f3503

CVE-2007-2353 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.apache.axis:axis. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.axis:axis — see the affected versions and patch details below.

Apache Axis allows Exposure of Sensitive Information to an Unauthorized Actor

Also known asGHSA-2c4w-2px5-9x3x

Published

Apr 30, 2007

Updated

Mar 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

27.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% 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.apache.axis:axis

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

Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installation path in the resulting exception message.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.axis:axis`	all versions	1.2`org.apache.axis:axis:1.2`

Affected Products

1 product · 1 configurations

Application

axisapache

1 version

1.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-29930remotemultiple✓ Verified

Apache AXIS 1.0 - Non-Existent WSDL Path Information Disclosure

by [email protected] · Apr 27, 2007

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.axis:axis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.axis:axis to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-2353 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Apache Axis 1.0 allows remote attackers to obtain sensitive information by requesting a non-existent WSDL file, which reveals the installation path in the resulting exception message.

O3 Security · Impact-Aware SCA

Is CVE-2007-2353 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

Timeline

First exploit

Apr 27, 2007

Disclosed

Apr 30, 2007

Last updated

Mar 20, 2026

Identifiers

CVE-2007-2353

GHSA-2c4w-2px5-9x3x

References

Advisorynvd.nist.gov · CVE 2007 2353 Webattrition.org Webosvdb.org Webexchange.xforce.ibmcloud.com Webgithub.com Webgithub.com · 32f35038ecae2c7a7f2e904b2289fd383f6f4d1f Webgithub.com · 2fdbb91c5e861e804db70cada188b1d7c1603513 Webgithub.com · 7ba89deb2eb21615630f18e96a35bfdec7f7cfed Packagegithub.com · axis axis1 java Evidencesecurityfocus.com

Related vulnerabilities

Also affects axis

This CVE is medium severity; 6 of 6 other CVEs affecting axis are rated as high or higher (top: critical).

CVE-2023-51441CVE-2023-40743CVE-2012-5784CVE-2019-0227CVE-2018-8032CVE-2014-3596

Same weakness: CWE-200

This CVE is medium severity; 1 of 2 other CVEs with CWE-200 is rated as high or higher (top: moderate).

CVE-2026-55098GHSA-m3qr-fvp4-78xjBrowse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 20, 2026

CVE-2007-2353 — axis

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-2007-2353 in your dependencies?