`CVE-2008-5720` seasar Mayaa

Affected software	seasar Mayaa
Severity	4.3 Medium CVSS 2.0
Fixed in	`1.1.23`
Weakness	Cross-site scripting (CWE-79)
Published	26 Dec 2008
Updated	16 Jun 2026

Description

Cross-site scripting (XSS) vulnerability in Mayaa before 1.1.23 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors involving the default error page for the org.seasar.mayaa.impl.engine.PageNotFoundException exception and possibly other exceptions.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 17 years ago.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS 1.3% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

Protection none
Action unverified
Review automated Upstream data
Record active

Decided by	Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding	This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.

Decided by

Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

Finding

This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

com.github.seasarorg.mayaa:mayaa 0 1.1.23 unbounded

Package	Introduced	Fixed	Last affected
`com.github.seasarorg.mayaa:mayaa`	0	`1.1.23`	unbounded

Products and versions

2 products, 69 version entries

Source	Vendor	Product	Scheme	Affected versions
osv	com.github.seasarorg.mayaa	mayaa	generic	＜ 1.1.23
nvd	seasar	mayaa	generic	0.1.0 · 0.1.0f · 0.1.1 · 0.1.2 · 0.1.3 · 0.2.0 · 0.3.0 · 0.4.0 · 0.9.0 · 0.9.1 · 0.9.2 · 0.9.3 · 0.9.4 · 0.9.5 · 0.9.6 · 0.9.7 · 0.9.7.1 · 0.9.8 · 0.9.9 · 0.9.10 · 0.9.11 · 0.9.12 · 0.9.13 · 0.9.14 · 0.9.15 · 0.9.16 · 0.9.17 · 0.9.18 · 0.9.19 · 0.9.20 · 0.9.20a · 1.0.0 · 1.0.0:beta1 · 1.0.0:beta2 · 1.0.0:beta3 · 1.0.0:rc1 · 1.0.1 · 1.0.2 · 1.0.3 · 1.1.0 · 1.1.0:beta1 · 1.1.0:beta2 · 1.1.0:beta3 · 1.1.0:beta4 · 1.1.0:beta5 · 1.1.0:beta6 · 1.1.1 · 1.1.2 · 1.1.3 · 1.1.4 · 1.1.5 · 1.1.6 · 1.1.7 · 1.1.8 · 1.1.9 · 1.1.10 · 1.1.11 · 1.1.12 · 1.1.13 · 1.1.14 · 1.1.15 · 1.1.16 · 1.1.17 · 1.1.18 · 1.1.19 · 1.1.20 · 1.1.21 · ≤ 1.1.22

Source

Vendor

Product

Scheme

Affected versions

osv

com.github.seasarorg.mayaa

mayaa

generic

＜ 1.1.23

nvd

seasar

mayaa

generic

0.1.0 · 0.1.0f · 0.1.1 · 0.1.2 · 0.1.3 · 0.2.0 · 0.3.0 · 0.4.0 · 0.9.0 · 0.9.1 · 0.9.2 · 0.9.3 · 0.9.4 · 0.9.5 · 0.9.6 · 0.9.7 · 0.9.7.1 · 0.9.8 · 0.9.9 · 0.9.10 · 0.9.11 · 0.9.12 · 0.9.13 · 0.9.14 · 0.9.15 · 0.9.16 · 0.9.17 · 0.9.18 · 0.9.19 · 0.9.20 · 0.9.20a · 1.0.0 · 1.0.0:beta1 · 1.0.0:beta2 · 1.0.0:beta3 · 1.0.0:rc1 · 1.0.1 · 1.0.2 · 1.0.3 · 1.1.0 · 1.1.0:beta1 · 1.1.0:beta2 · 1.1.0:beta3 · 1.1.0:beta4 · 1.1.0:beta5 · 1.1.0:beta6 · 1.1.1 · 1.1.2 · 1.1.3 · 1.1.4 · 1.1.5 · 1.1.6 · 1.1.7 · 1.1.8 · 1.1.9 · 1.1.10 · 1.1.11 · 1.1.12 · 1.1.13 · 1.1.14 · 1.1.15 · 1.1.16 · 1.1.17 · 1.1.18 · 1.1.19 · 1.1.20 · 1.1.21 · ≤ 1.1.22

References

URL	Tags
https://exchange.xforce.ibmcloud.com/vulnerabilities/47623	WEB
https://github.com/seasarorg/mayaa	PACKAGE
https://web.archive.org/web/20090622223640/http://secunia.com/advisories/33333	WEB
https://web.archive.org/web/20200301074809/http://www.securityfocus.com/bid/33015	WEB
http://jvn.jp/en/jp/JVN17298485/index.html	WEB
http://jvndb.jvn.jp/en/contents/2008/JVNDB-2008-000085.html	WEB
http://mayaa.seasar.org/news/vulnerability20081225.html	WEB
http://osvdb.org/51007
http://secunia.com/advisories/33333
http://www.securityfocus.com/bid/33015

URL

Timeline

Published	2008-12-26	By the CVE Program.
NVD record modified	2026-06-16	NVD's own last-modified date for this record.

Published

2008-12-26

By the CVE Program.

NVD record modified

2026-06-16

NVD's own last-modified date for this record.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: com.github.seasarorg.mayaa:mayaa

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven matched Mitigation candidate Open-source Maven artifact indexed by OSV (Maven packages: com.github.seasarorg.mayaa:mayaa). The source is public, which makes an ARMR patch rule a candidate; nothing here establishes that one can be written.

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold decided it matched No exploit published MEDIUM severity, no CISA or VulnCheck KEV listing, no public PoC clearing the evidence bar, no CISA exploitation finding, and not in an Oracle advisory — none of the signals we act on is present.

24 no-exploit-published skipped Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

seasar mayaa not tracked cpe:2.3:a:seasar:mayaa:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗